Skip to content
OnchainQueries

OQ — D00 · Datasets

37 Solana programs. 1,074 typed tables. OnchainQueries reads each program's interface definition and produces one table per event and one per instruction, with the real field names — so you are reading sol_amount, not a byte offset.

Programs decoded
37
Tables total
1,074
Event tables
220
Instruction tables
854

37 of 37 programs

OQ — D01By family

Every table follows the same shape, so once you can read one protocol you can read all of them.

DEX & Trading

21 programs

Aggregators, AMMs, concentrated liquidity, order books and perpetuals — every swap decoded to its instruction and its event.

Launchpads & Tokens

9 programs

Bonding curves, graduations and migrations, from creation through to the pool that outlives it.

Lending & Yield

6 programs

Reserves, obligations, farms, vaults and liquidity locks — positions and the instructions that move them.

Liquid Staking

1 programs

Stake pool deposits, withdrawals and validator management.

OQ — D02Shape of a query

Tables resolve through the catalog before a source query is issued, so an unknown table or alias fails immediately rather than halfway through a scan.

trades.sql
SELECT  date_trunc('hour', ts) AS hour,  count_if(is_buy) AS buys,  count_if(NOT is_buy) AS sells,  sum(sol_amount) AS sol_volumeFROM pump_fun_solana.pump_fun_evt_trade_eventWHERE ts >= {{start_time}}GROUP BY hourORDER BY hour;
Event table
pump_fun_solana.pump_fun_evt_trade_event
Short alias
pump_fun.trade_event
Instruction table
pump_fun_solana.pump_fun_call_buy
Physical catalog
prod_solana_eventstream
OQ — D03Coverage, honestly

Do all 37 programs have event tables?

No. Sixteen of them expose instruction tables only, because their IDL declares no events. Those programs are still fully queryable through their call_ tables — you are reading the instruction and its accounts rather than an emitted event. Each dataset page states which it has.

Are the cross-protocol convenience views a drop-in replacement?

Not yet. dex_solana.trades and dex.swaps exist when the required Pump Fun columns are present, but their coverage is Pump Fun only — not the full set of Solana DEX protocols OnchainQueries decodes. token_bought_symbol, token_sold_symbol and amount_usd are currently NULL. Do not use them for market-wide Solana totals.

How do I know which tables a result actually touched?

Every result manifest carries a source_coverage.tables field listing the physical tables the query read, along with the catalog hash and high-watermark slot used to plan it. When coverage matters, read it rather than assuming.

Can I browse the catalog from the CLI?

Not currently. There is no SHOW TABLES or DESCRIBE, and no CLI catalog browser. This page and the dataset pages are the catalog; only tables present in the live catalog are queryable.

Every dataset page lists its real tables, both name forms, and a query you can paste straight into the CLI.

Start queryingRead the docs