Balances for addresses on EVM networks.
tokens_<chain>.balances
table for queries.
Mirroring the approach of this query is currently the fastest way to get started with the token balances dataset.tokens_<chain>.balances_daily
table contains all daily token balances across all addresses and on EVM-compatible networks. This dataset encompasses:
tokens_<chain>.balances
table, which is updated . For the balance to be queried, the address must have appeared in any of the following tables:
to
/from
addresses, Ethereum-specific withdrawals, and block mining/validator activities.to
/from
addresses in the transfer events. If the token is a non-standard ERC20 token, the balance might not be updated until we detect a standard ERC20 transfer event. Known issues currently include ERC4626 tokens and rebasing tokens like stETH or $ampleforth. We are working on improving the range of balance changes that we detect.to
/from
addresses.Transfer
event, or for addresses that have not been involved in any transactions or NFT transfers. If there is a specific token that does not emit the Transfer
event, but has a different event for token transfers, please let us know and we will see if we can include it in our balance calculations.
tokens_<chain>.balances
table, which contains granular balance changes for each address, token combination per block. This table is updated in near real-time and is used to calculate the daily balances. This table is useful for more granular analysis, such as tracking the balance changes of a specific address over time.
However, the tokens_<chain>.balances
table is very large and is not suitable for querying large time ranges or for querying balances for many addresses at once. For these use cases, the tokens_<chain>.balances_daily
table is more suitable.
The tokens_<chain>.balances
table adds a new row every time a balance changes but does not carry the balance forward for every block. Instead, it only creates a new row for a balance change of an address and token combination.