The chain’s own record is queryable for ApeChain, with its eligible catalog layers above it.
The chain’s own record sits in the apechain dataset: one row per block, transaction, log and internal call. Everything above that sits in the catalog, where the ApeChain rows are selected with chain_id = 'apechain'.
The section mirrors the catalog itself: the core entities, then the market verticals with data on ApeChain.
Layers
| Layer | Since | What it holds |
|---|
| Raw | 2024-08 | Blocks, transactions, logs and internal calls. |
| 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. |
Filtering
chain_id reads apechain in every catalog table that mentions a chain, so the same filter selects ApeChain 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.
