Query Solana tokens

​

What’s covered

​

Access

​

Example queries

​

Recent transfers for a mint

SELECT
  block_time,
  tx_id,
  source_owner,
  destination_owner,
  amount
FROM solana.transfers
WHERE mint = '{mint}'
  AND action = 1
ORDER BY block_time DESC
LIMIT 100;

​

Transfer volume for a mint

SELECT
  toDate(block_time) AS day,
  count() AS transfer_count,
  sum(amount) AS volume_base_units
FROM solana.transfers
WHERE mint = '{mint}'
  AND block_time >= now() - INTERVAL 7 DAY
  AND action = 1
GROUP BY day
ORDER BY day DESC;

​

Recent wallet transfer history

SELECT
  block_time,
  tx_id,
  mint,
  source_owner,
  destination_owner,
  amount
FROM solana.transfers
WHERE (source_owner = '{wallet}' OR destination_owner = '{wallet}')
  AND block_time >= now() - INTERVAL 7 DAY
  AND action = 1
ORDER BY block_time DESC
LIMIT 100;

​

Instruction activity for a program

SELECT
  block_time,
  tx_id,
  instruction_name,
  accounts,
  args
FROM solana.instructions
WHERE executing_account = 'TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA'
  AND instruction_name = 'transferChecked'
  AND action = 1
ORDER BY block_time DESC
LIMIT 50;

​

Reconstruct transfers with instruction context

SELECT
  t.block_time,
  t.tx_id,
  t.mint,
  t.source_owner,
  t.destination_owner,
  t.amount,
  i.instruction_name,
  i.executing_account
FROM solana.transfers AS t
JOIN solana.instructions AS i
  ON t.instruction_id = i.instruction_id
WHERE t.mint = '{mint}'
  AND t.action = 1
  AND i.action = 1
ORDER BY t.block_time DESC
LIMIT 50;

​

Query tips

1. Filter on indexed columns — for transfers, lead with mint and block_time; for instructions, lead with executing_account, instruction_name, and block_time.
2. Query wallets via owners — SPL transfers expose token accounts in source / destination. Use source_owner / destination_owner (or account_owners on instructions) to filter by holder wallet.
3. Use the solana.* prefix — Solana tables use this prefix
4. Scope to active rows — filter action = 1 (or 'added') the same way you would on Base; small re-orgs are possible at the tip. Prefer instruction_id as the stable id across reprocessing.
5. Scope time ranges — about 3 months of history is retained; always bound block_time for faster queries.

​

Scope and limitations

• Programs: Instruction decoding focuses on SPL Token and Token-2022. solana.transfers also includes native SOL transfers from the System program.
• Not a full instruction set: Arbitrary program coverage is not available yet.
• History: Approximately 3 months of historical data available as of 12-Aug-2026 launch.
• Beta: Schema and coverage may change during public beta.

​

Learn more

• Schema reference — full solana.instructions and solana.transfers column definitions
• Quickstart — run your first SQL API query
• Best practices — indexing and query patterns
• FAQ — networks, limits, and re-org handling