The chain’s own record is queryable for opBNB, with its eligible catalog layers above it.
The chain’s own record sits in the opbnb dataset: one row per block, transaction, log and internal call. Everything above that sits in the catalog, where the opBNB rows are selected with chain_id = 'opbnb'.
The section mirrors the catalog itself: the core entities, then the market verticals with data on opBNB.
Layers
| Layer | Since | What it holds |
|---|
| Raw | 2023-08 | Blocks, transactions, logs and internal calls. |
| Projects | 2023-08 | Daily Fees and Revenue for each tracked project, broken out to opBNB. |
| Tokens | In progress | Every ERC-20 transfer, both sides of every balance move, holder balances at query time, and daily prices. |
| Accounts | In progress | Wallets and contracts labeled with the projects that own them. |
| Bridges | 2023-09 | Cross-chain transfers that left opBNB or arrived on it, matched leg to leg. |
Filtering
chain_id reads opbnb wherever a catalog table carries a chain, so the same filter selects opBNB everywhere. Some shapes ask for something else. The asset tables key on the asset or its deployment, so the chain comes from dimensions.asset_tokens, as the query below does. Project and app totals span every chain a project runs on, so one chain’s share reads from metrics_project_chains and metrics_app_chains. A bridge transfer has a chain on each end and carries source_chain_id and destination_chain_id.
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.
