App builder

Watch every address from one wallet dashboard
without touching a private key.

Name the public addresses you follow and Netiva’s AI builds a web app that reads their balances and transfers from the block explorer API you choose, labels each one and emails you when coins move.

Start building free More app ideas
Starter prompt

Build a watch-only crypto wallet web app for a foundation treasury. Keep an Addresses collection with the chain, the public address, a label, an owner group and a public flag. Every 15 minutes, read each address’s native and token balances and any new transfers from our block explorer API, converting raw amounts with each token’s decimals. Show holdings by chain priced from a market-data provider, an activity feed with pending transfers first and a public page listing the addresses we choose to publish. Signers sign in; the public page is open to everyone.

Build it in Netiva Paste the prompt into a new workspace and adjust it to your business.
Overview

Who this wallet dashboard is for

Cold storage, a multisig treasury and the addresses your community keeps an eye on are all public — but reading them means a separate explorer tab for each one and a string of hex where a name should be. Nobody remembers which address holds the grant pot. A wallet dashboard built with Netiva works as a blockchain wallet app you own: the addresses you watch sit in one collection, balances and transfers come from the explorer or indexer API you choose and every address carries the label your team actually uses.

Key features

What your wallet dashboard can do

  • Addresses with names, not hex

    Every address you follow gets a label, a chain, an owner group and a wallet type, so the dashboard reads like your treasury instead of a column of 42-character strings.

    • Groups such as cold storage, multisig, payouts and grants
    • One row per address per chain, with the date you started watching
    • Saved views by group, by chain or by who holds the keys
    • Private notes on an address that the public page never shows

  • Balances from your explorer API

    A scheduled job calls the block explorer or indexer you signed up with, using your key stored securely, and writes each address’s native and token balances into a collection with the time it read them.

    • Raw on-chain amounts converted with each token’s decimals
    • Holdings valued at prices from the market-data provider you pick
    • Read time and read status on every balance row
    • A rate-limited or failed read flagged rather than left to look current

  • An activity feed you can read

    Transfers land in one feed with the amount, the asset, the direction and the address on the other side, matched to your own labels when the counterparty is a wallet you also watch.

    • Pending transfers at the top, confirmed ones dated by block time
    • Filters by chain, address, asset, direction and month
    • Every row linked to its transaction on your explorer
    • Moves between your own addresses marked as internal

  • Alerts for signers, a page for everyone

    Set a size per address and the app emails the group when something larger moves. Addresses you mark public appear on a transparency page anyone can check, and the rest stays behind sign-in.

    • An email when an amount over your threshold arrives or leaves
    • A daily digest of the day’s transfers for the finance lead
    • Signers sign in to see private addresses and internal notes
    • A public page with balances, read times and explorer links
Data model

The collections behind it

Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.

Addresses

The public addresses you follow, with the names your team uses for them.

  • Label (required) Operating multisig, grant pot, founder cold storage Text
  • Chain (required) One row per address per chain, since the same account can hold on several Text
  • Address (required) A public address or an account’s extended public key — never a private key or seed Text
  • Wallet type Cold storage, hot wallet, multisig or exchange deposit Text
  • Owner group Who the balance belongs to; used to total holdings and route alerts Text
  • Published (required) Yes or no — decides whether the address appears on the transparency page Text
  • Alert above Transfer size that triggers an email for this address Number
  • Notes Signer names, hardware model, why the address exists; kept off the public page Paragraph

Assets

The coins and tokens your watched addresses hold, identified by contract.

  • Name (required) Text
  • Symbol (required) A display label only; several tokens can share one Text
  • Chain (required) Text
  • Contract address Blank for a chain’s native coin; this is what tells two tokens with the same symbol apart Text
  • Decimals (required) How far to shift the raw amount: 18 for ether and most ERC-20 tokens, 8 for bitcoin Number
  • Price ID The asset’s ID at your market-data provider, left blank for anything you don’t value Text
  • Review status (required) Approved, unreviewed or spam; unreviewed assets stay out of totals Text

Balances

What each address held at the last read, one row per address and asset.

  • Address (required) Relation to Addresses
  • Asset (required) Relation to Assets
  • Quantity (required) Already converted with the asset’s decimals Number
  • Value Quantity at your provider’s price, in your reporting currency Number
  • Read at (required) Date & time
  • Read status (required) OK, rate limited or failed on the last run Text

Transfers

Every movement in or out of a watched address, as the chain recorded it.

  • Address (required) Relation to Addresses
  • Asset (required) Relation to Assets
  • Direction (required) In, out, internal between addresses you watch, or the network fee on a transfer you sent Text
  • Quantity (required) Number
  • Counterparty The address on the other side; shown with its label when you watch it too Text
  • Transaction hash (required) The chain’s transaction ID, linked out so anyone can check the transfer themselves Text
  • Block time When the transaction was included in a block; blank while it is still pending Date & time
  • Status (required) Pending, confirmed or dropped when a pending transaction was replaced Text

Required field. Types are Netiva collection field types.

Screens

Pages and screens to start with

A typical first version. Ask the agent for more, or annotate the preview to change any of them.

  • Watched addresses

    Every address you follow with its label, chain, group, native and token balances and the moment each figure was last read.

    Signed-in users

  • Address detail

    One address in full: balances by asset, its transfers newest first, the group and wallet type it belongs to and a link out to your explorer.

    Signed-in users

  • Activity

    Transfers across every watched address, pending ones first, filtered by chain, direction, asset or month.

    Signed-in users

  • Token review

    Assets that turned up from contracts nobody has approved, with the contract address, the date first seen and buttons to approve one or mark it spam.

    Your team

  • Monthly statement

    Per address: opening balance, what came in, what went out, network fees and closing balance for the month, ready to hand to a bookkeeper.

    Your team

  • Transparency

    The addresses you chose to publish, their balances, when each was read and a link so readers can check the figure on-chain for themselves.

    Public
How it works

From prompt to a live wallet dashboard

  1. List what you watch

    Tell Netiva which chains you hold on, which public addresses you follow and how you group them. The agent drafts collections for addresses, assets, balances and transfers.

  2. Point it at your explorer

    Store your block explorer or indexer key securely and paste your addresses into the grid. The collection assistant can fill chains, labels and token decimals across many rows before the first read runs.

  3. Check one address against the chain

    Open the dashboard in the live preview next to your explorer and compare a single address. If a token amount is shifted by its decimals, annotate the row and the agent fixes the conversion.

  4. Publish and decide what’s public

    Publish in one click, invite your signers to sign in and mark the addresses that belong on the transparency page. Every change is checkpointed, so a threshold or a published address is easy to roll back.

Why Netiva

Netiva vs a traditional build

Building a wallet dashboard with Netiva compared with a traditional build
Criterion With Netiva Traditional build
Checking balances One labeled list, read on a schedule, with the read time beside every figure An explorer tab per address and a spreadsheet of totals that goes stale by lunchtime
Treasury transparency A published page with the addresses you chose, their balances and a verification link for each Addresses posted in a forum thread that readers paste into an explorer one at a time
Getting started Describe what you need in chat and watch it take shape in a live preview Hire developers, or stitch together templates, plugins and a hosting plan
Content and data Built-in collections with nine field types, bound straight to your pages Set up and connect a separate database or CMS
Making changes Ask the agent; every change is checkpointed and reversible File a ticket, wait for a sprint, redeploy
Hosting and domain Global hosting and automatic SSL; connect a custom domain from the Starter plan Buy hosting, then install and renew SSL certificates yourself
Code ownership Clean production code you own and can export Locked into a template, plugin or agency setup
Examples

Ways teams use it

  • A foundation treasury on two chains

    Five multisig addresses hold the operating and grant funds. Signers see balances and the month’s transfers in one place, the finance lead exports the statement for the bookkeeper and nobody needs a key to read any of it.

  • A holder watching cold storage

    A handful of addresses sit behind a hardware wallet that stays offline. The dashboard follows them without the seed phrase ever meeting a browser, and an email whenever anything leaves is the warning that matters.

  • A community checking a project’s wallets

    Moderators publish the project’s addresses so readers confirm balances themselves instead of trusting a screenshot, and a short monthly note explains what the grant address paid out.

Good to know

Before you build

  • Watch-only, and keep it that way

    The dashboard reads public data. Never paste a seed phrase or private key into it, and don’t let a balance on screen stand in for approval to send. Signing stays in the wallet software your signers already use; the app records what the chain has already done.

  • One address is rarely a whole wallet

    Bitcoin wallets spread coins across many addresses, change addresses included, so list them all or watch the account’s extended public key — which shows the account’s whole payment history to whoever holds it. An EVM account is one address, but each chain needs its own read.

  • Your explorer sets the pace

    Pick a block explorer or indexer, read its terms and rate limits and size the refresh to fit. Token transfers and deep history usually cost more than current balances, coverage is thinner on newer chains, and a missed read leaves the last figures standing until the next one.

  • Tokens you never asked for

    Unsolicited tokens turn up in public addresses, and anyone can deploy a token with a familiar name and symbol — only its contract address tells them apart. Keep new assets unreviewed and out of totals until someone checks them, and never pay an address copied out of the feed.

Compliance note

Netiva builds the dashboard only. It reads public blockchain data through the explorer or indexer API you choose, and it never holds keys, moves or mines coins, places trades or gives investment advice; values come from your market-data provider. Balances are a snapshot from the last read, so say that on any public page. Anything that signs transactions or handles other people’s funds belongs with your own licensed provider, after legal review where you operate.

FAQ

Questions about building a wallet dashboard

Can a wallet dashboard built with Netiva move coins?

No, and that’s the point. It reads public blockchain data through the API you connect, and it never holds a private key, a seed phrase or a hardware wallet. Netiva doesn’t hold, move or mine coins and doesn’t place trades. Sending stays where it belongs, in the wallet software your signers already use, and the dashboard shows the transfer once the chain has recorded it.

Where does a blockchain wallet app get balances and transfers?

From a block explorer or indexer you sign up with. Netiva apps can call any REST API with the key stored securely, so a scheduled job asks your provider about each watched address and writes what comes back into your collections. Coverage, history depth and rate limits differ by chain and by provider plan, so check what yours returns for the chains you hold on before you set the interval.

How do I watch a whole Bitcoin wallet instead of one address?

A Bitcoin wallet spreads coins across many addresses, change addresses included, so a single one rarely shows the full balance. List each address you use, or hand the app the account’s extended public key and let it derive them. BIP-32 describes that for audits: an extended public key shows every payment in and out but not one secret key. It shows them to anyone else who gets it, so treat it as sensitive.

Why is a token balance off by a lot of zeros?

Because chains store amounts as whole numbers. An ERC-20 contract’s decimals value says how far to shift the point — 8 decimals means dividing by 100,000,000 — and ether and most tokens use 18, while bitcoin uses 8. Keep the decimals on the asset row and have the scheduled read convert once, on the way in, so every screen and every export shows the same figure.

How current are the balances, and when is a transfer settled?

Balances are as fresh as the last scheduled read, which is why each row carries its read time. A new transfer starts as pending and can still be replaced. Bitcoin clients have long treated six blocks deep as settled, roughly an hour at a 10-minute average block interval, and an Ethereum block takes about 15 minutes to finalize. Show the status instead of implying every figure is live.

Can we publish our treasury addresses without exposing the rest?

Yes. Each address carries a published flag, so the transparency page lists only what you mark, with balances, read times and a link to verify each one on an explorer. Signers sign in for private addresses and notes. You can build and preview on the free plan, and publishing on your own domain starts with the Starter plan. The code stays yours to read, export and roll back.

Keep exploring
All ideas
Compare

How Netiva compares

All comparisons

Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.

Build your wallet dashboard today

Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.

Start building free Browse more ideas