Walletbalance data
What an address held, and when it held it. We deliver that three ways: as tables in your datashare when you want to run it as SQL over history, as an API when you want an answer for one wallet right now, and as a batch call when you want many at once.
Three ways to read a balance
EthereumIn practice
Where teams use it
Treasury, audit and reporting teams read balances for chains like Ethereum, Base and Solana: as tables when the question spans history, as a single API call when it is one wallet right now, and as a batch call when it is a whole book of wallets. The three shapes are built per chain, and coverage for every chain is listed on the chain coverage page.
In the datashare
Point-in-time balance tables
Balance tables ship inside the chain's datashare, so a balance series is a join away from the transfers that produced it. What a table holds depends on how the chain accounts for balances. For chains like these:
Base
BSC
PolygonSOL and SPL token balances at block level and in ten-minute buckets.
Native and token balances per ledger, each row carrying its previous balance.
Balance tables for other chains are added on request. Tell us the chains you care about and we will confirm what each one takes before you plan around it.
One call, one wallet
Real-time balances API
One REST call per address. We resolve the tokens that wallet has held and read their balances: current, or at the block you name.
Live for chains like:
Polkadot- Solana has its own service: account and token balances at ten-minute granularity through history, and down to one second on the live path.
- Polkadot returns native free, reserved and frozen amounts plus assets and foreign assets, for any time from 16 October 2025 onward.
- The EVM chains we support answer on the same endpoint shape, so one integration covers them all.
Other chains are added on request. Send us the chains you need and we will confirm what each one takes.
One call, many wallets
Batch wallet-token-balance API
The same service in bulk. Use it when you are pricing a book of wallets rather than answering a single lookup:
Named tokens
Ask for up to ten named tokens on one wallet in a single call, skipping discovery entirely.
Wallet scan
Or scan a wallet: walk every token that wallet has ever touched, paginated.
Many wallets
Or send up to ten wallets in one request and get a holdings set back for each.
Same response shape across all three, so one parser covers the lot.
Use cases
What teams build with it
- Portfolio and treasury reporting across chains from one interface.
- Month-end reconciliation against a balance as of a specific block.
- Audit and compliance evidence that a wallet held what it says it held, when it says it did.
- Cost-basis and tax calculations that need a balance series rather than a current figure.
- Risk and exposure monitoring on a set of watched addresses.
The rest of the platform
Other ways to get the data
Get started
Check a balance against your chain
Send us the chains and the wallets you care about and we will tell you which of the three shapes fits, and what it takes to cover the rest.