Most of the catalog is queryable for Solana, from the slots themselves to the daily activity of the projects that run on it.
The chain’s own record sits in the solana dataset: one row per slot, transaction, instruction, account touched and reward paid. Everything above that sits in the catalog, where the Solana rows are selected with chain_id = 'solana'.
The section mirrors the catalog itself: the core entities, then the market verticals with data on Solana.
Layers
| Layer | Since | What it holds |
|---|
| Raw | 2020-10 | Slots, transactions, instructions, account balance moves and rewards. |
| Projects | 2020-10 | Daily Fees and Revenue for each tracked project, broken out to Solana. |
| Apps | 2021-04 | Daily Trading volume, TVL, Fees and Revenue for each tracked app, broken out to Solana. |
| Assets | 2020-10 | Every curated asset issued on Solana, with daily supply, holders and transfer activity. |
| Tokens | 2020-03 | Every SPL transfer, both sides of every balance move, holder balances at query time, and daily prices. |
| Accounts | In progress | Wallets and programs labeled with the projects that own them. |
| Contracts | 2021-01 | Every program deployed on Solana, with the account that deployed it. |
| Stablecoins | 2020-10 | Every stablecoin issued on Solana: supply, holders and transfers. |
| Real-world assets | 2023-03 | Tokenized stocks, funds and commodities issued on Solana, tracked against their underlying instruments. |
| DEX | 2022-03 | Trading pools and their daily volume, per pool and per traded token pair. |
| Bridges | 2025-05 | Cross-chain transfers that left Solana or arrived on it, matched leg to leg. |
Filtering
chain_id reads solana wherever a catalog table has a chain column, so the same filter selects Solana 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, in source_chain_id and destination_chain_id.
Solana addresses are base58 and case-sensitive, so they are matched exactly as the chain writes them. An EVM address is lowercased before it is stored; a Solana mint, program or wallet address is not, and EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v matches only in that spelling.
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.
