Most integrations should start with Tokens / Trades / Wallets rather than here —
the higher-level products are cheaper to query and already de-noised.
What’s inside
| Dataset | Key fields |
|---|---|
| Blocks | number, hash, parentHash, timestamp, gasUsed, baseFeePerGas, miner |
| Transactions | hash, from, to, value, input, status, gasUsed, effectiveGasPrice |
| Logs / Events | txHash, logIndex, address, topics[], data, removed |
| Gas metrics | blockGasUsage, chainGasOracle (EIP-1559 base / priority fees) |
| Chain state | latestBlock, finality, reorgsLast1h |
Coverage & freshness
- Raw data from every supported chain, back-filled to genesis where possible.
- Latency: blocks and logs delivered within 1–2 s of finalization.
Access
REST
/v2/blockchain, /v2/blockchain/{chain}/latest_block.Kafka
{chain}.dex.trades, {chain}.v1.transfers.proto, {chain}.balances Protobuf topics per chain.GraphQL
Query blocks joined with transactions and decoded events.
SDK
Typed wrappers for blocks/transactions/logs.
Common use cases
- Independent verification of a higher-level data point
- Custom indexing pipelines that need raw logs
- Gas-price oracles and fee-estimation services
- Chain-health dashboards (reorgs, uncle rate, base-fee drift)
Billing
Raw-data endpoints charge per item returned. Kafka topics priced per delivered message, discounted in streaming tiers.Next
Kafka topic catalog
Per-chain list of raw topics and schemas.
Data freshness & SLA
Latency expectations per chain and per surface.