Onchain analytics data for your own warehouse
SQD sits at the extract-and-decode end of the analytics pipeline. It streams decoded events, transactions, and traces from one endpoint across 225+ networks, from genesis to head, and you model and serve them as SQL in the warehouse you already run. The Portal is not a SQL endpoint; the SQL is yours.
Built for Analytics at scale
Single endpoint, 225+ networks
One POST to portal.sqd.dev returns logs, transactions, traces, and state diffs from any supported chain, with no per-chain RPC setup and no reconciliation across providers. Apply the contract ABI to decode, or let the Pipes SDK decode for you.
Full archival depth from genesis
Every block, transaction, and event log from block 0 to head, on every chain, through the same query as live data. Backfill a contract's full history in one streamed range request instead of paginating eth_getLogs against per-call block-range caps.
Real-time NDJSON streaming
Stream new blocks, events, and state changes as NDJSON over HTTP, the same query shape you use for history. No WebSocket to manage, no polling loop. Figures over unfinalized blocks are provisional until finality, as in any streaming pipeline.
Direct warehouse integration
Pipe decoded data into ClickHouse, Postgres, MongoDB, SQLite, or Parquet on S3 with the Pipes SDK, plus a custom-target API for BigQuery, Snowflake, and Databricks. Your BI tool then queries the resulting store with ordinary SQL.
Extract and decode here, model and serve in your warehouse
Every dashboard is the end of a four-stage pipeline: extract the blocks and logs, decode the raw hex into named events, model it into tables shaped around your questions, and serve it from a warehouse a BI tool queries with SQL. SQD owns the first two stages and streams the result into the store you already run. The Portal is not a SQL endpoint; the SQL is yours.
The numbers are real and reproducible. One extract for USDC, USDT, and DAI transfers over a fixed 1,000-block window on Ethereum (18,000,000 to 18,001,000) returns 22,318 transfers worth about $542M. Same window, same totals on every run.
- USDC$318.8M
- USDT$203.4M
- DAI$19.5M
The extract is one filter on the Transfer topic across the three token contracts (multiple addresses in one filter is OR logic):
That streams raw logs as NDJSON; the amount is hex in data. Decode against the ERC-20 ABI (or let the Pipes SDK do it), load into ClickHouse, then it is a GROUP BY. The full extract-decode-rollup walkthrough is in the onchain analytics guide.
Reach the same data at the level your stack needs
The data layer itself
A streaming HTTP endpoint serving filtered logs, transactions, traces, and state diffs, with full history, in any language. You apply the contract ABI and aggregate the result. Teams run it in production as the data source, in place of RPC for history and bulk reads.
- - Any language or stack
- - Full history from genesis
- - You decode and aggregate
- - NDJSON over HTTP, no SDK required
Decode and load, built in
Sits on top of the same API in TypeScript: decodes logs into typed events and streams them into a target store, with progress tracking and reorg rollback handled for you. Built for a durable analytics pipeline rather than one-off queries.
- - ClickHouse, Postgres, Parquet/S3 targets
- - Custom-target API (BigQuery, Snowflake)
- - Decoding and typed events built in
- - Progress tracking and reorg rollback
Try the Portal API
Live queries against real blockchain data. Pick a network, choose a query, hit run.
The public endpoint is free for development. See plans for dedicated portals and higher limits.
Basebase-mainnet/streamWhat teams build with SQD
Other ways teams use SQD
Each of these runs on the same SQD data layer.
A DEX swap settles its token movement in nested internal calls; an event-log-only feed sees the receipt, not the execution.
A raw event log is hex-encoded topics and data.
Query any address and get its history: token transfers, native and internal value, NFT movements, and contract calls, across 225+ networks through one query shape.
Onchain, every stablecoin movement is a Transfer event: a mint is a transfer from the zero address, a burn is a transfer to it, a payment is one between two wallets.
A tokenized treasury fund is a regulated security that lives on a public chain.
Most indexers give you event logs.
The same JSON-shaped request reads EVM logs, Solana instructions, and Bitcoin inputs and outputs, with no schema, no deploy, and no sync wait.
One declarative query reads Solana program activity by program ID and discriminator, and surfaces the failed and uncommitted calls most tools drop.
How blockchain history feeds analytics dashboards. The data pipeline, the common metrics, and how this is done in tools like Dune and in-house BI.
Frequently asked questions
How do I query SQD data from a dashboard?
What's the difference between SQD and Dune?
Can I export to BigQuery or Snowflake?
Your blockchain data infrastructure, handled.
Private Portal. Dedicated. Validated. Managed. Tell us what you're building, we'll show you what it looks like on SQD.
validated data
for Enterprise
serving data