Skip to main content
One row per holder of one stablecoin deployment, computed at query time from the transfer history by functions.calculate_latest_token_balances and functions.calculate_historical_eod_token_balances. balance is the holder’s amount in whole token units, and each call takes a chain, a token address and a token standard from Registry. Coming: a curated pair for stablecoins. functions.calculate_latest_asset_token_balances and functions.calculate_historical_eod_asset_token_balances cover the tokenized asset registry, which every stablecoin here belongs to. They refuse rather than returning a number where a deployment cannot be modelled, so a figure they give back is one that has been checked. In progress: under test, not yet served. The generic pair above also accepts these tokens, and will answer for a rebasing stablecoin with a number that drifts below the chain. Both signatures are identical and documented at Tokens ▸ Balances. What the curated pair covers, and which stablecoins it declines, is at Assets ▸ Balance changes.

Columns

ColumnTypeDescription
balance_dateDATEDay the balance moved. Returned by calculate_historical_eod_token_balances, which writes a row per day an account’s balance changed.
account_addressSTRINGAccount holding the balance. On Solana this is the token account; dimensions.accounts resolves the wallet behind it.
balanceBIGNUMERICEnd-of-day balance in whole token units, already scaled down by decimals. calculate_latest_token_balances returns the last one per account, positive balances only.

Sample queries

Each call adds up the whole balance-change history of one deployment; a daily holder count is cheaper read from metrics_assets.holders_native_daily on Metrics. Addresses are lowercased on input, so a checksummed address pasted from an explorer resolves.