Skip to main content
Most of the catalog is queryable for BNB Smart Chain, from the blocks themselves to the daily activity of the projects that run on it. The chain’s own record sits in the bsc dataset: one row per block, transaction, log and internal call. Everything above that sits in the catalog, where the BNB Smart Chain rows are selected with chain_id = 'bsc'. The section mirrors the catalog itself: the core entities, then the market verticals with data on BNB Smart Chain.

Layers

LayerSinceWhat it holds
Raw2020-04Blocks, transactions, logs and internal calls.
Projects2022-09Daily trading and bridge volume for each tracked app and project, broken out to BNB Smart Chain.
Assets2020-09Every curated asset issued on BNB Smart Chain, with daily supply, holders and transfer activity.
TokensIn progressEvery ERC-20 transfer, both sides of every balance move, holder balances at query time, and daily prices.
AccountsIn progressWallets and contracts labeled with the projects that own them.
Stablecoins2020-09Every stablecoin issued on BNB Smart Chain: supply, holders and transfers.
Tokenized assets2023-02Tokenized stocks, funds and commodities issued on BNB Smart Chain, tracked against their underlying instruments.
DEX2023-03Trading pools, their daily volume, value locked and fees.
LendingIn progressThe lending markets deployed on BNB Smart Chain, the asset each one lends, and the lending facts.
Bridges2022-09Cross-chain transfers that left BNB Smart Chain or arrived on it, matched leg to leg.

Filtering

chain_id reads bsc in every catalog table that mentions a chain, so the same filter selects BNB Smart Chain everywhere. Bridge transfers are the one exception: a transfer has a chain on each end and carries source_chain_id and destination_chain_id instead.
Every table splits by day: the raw and event tables on block_timestamp, the daily tables on timestamp. Bound that column in every query; without a bound the query reads the whole table.