Skip to main content

​
Description

The Raw Data suite provides direct access to on-chain execution artifacts with cryptographic verification metadata. These endpoints deliver the foundational blockchain primitives that power all derived datasets. Each endpoint includes lineage fields (_tracing_id) that link records back to their on-chain origins.

​
Endpoint Matrix

EndpointSummaryDataset IDTypical Latency
POST /evm/raw/blocksRetrieve canonical EVM blocks with integrity metadata0101< 200 ms
POST /evm/raw/blocks/summaryAggregated block metrics (throughput, fees, participants)Derived< 150 ms
POST /evm/raw/transactionsExecuted transactions with gas accounting and lineage0102< 200 ms
POST /evm/raw/logsDecoded event logs with topic filters0103< 200 ms
POST /evm/raw/contractsContract deployment metadata keyed by address0104< 200 ms
POST /evm/raw/function-resultsDeterministic contract call outputs versioned by block0105< 250 ms

​
Parameter Conventions

​
from_block
number
Starting block height (inclusive) for range queries.
​
to_block
number
Ending block height (inclusive) for range queries.
​
from_timestamp
string
Starting timestamp (ISO-8601). If it falls between blocks, the next block after this timestamp is used.
​
to_timestamp
string
Ending timestamp (ISO-8601). If it falls between blocks, the last block before this timestamp is used.
​
block_numbers
number[]
Explicit list of block heights for precise lookups.
​
tx_hashes
string[]
Parent transaction hashes (hex string, 32 bytes, no 0x prefix) for targeted retrievals.
​
block_hashes
string[]
Block hashes (hex string, 32 bytes, no 0x prefix) for exact matching.
​
contract_addresses
string[]
Contract addresses (hex string, 20 bytes, no 0x prefix) to scope results to specific contracts.
​
chain_id
number
required
Chain identifier for the target EVM network. See Chain enumeration for supported values.
​
cursor
string
Pagination cursor returned from previous responses.
​
limit
number
Maximum number of records to return.

​
Usage Guidance

  • Start with blocks — Use /evm/blocks to establish time ranges before querying transactions or logs
  • Batch array filters — Prefer array filters (block_numbers, tx_hashes) over range queries for better performance
  • Join via _tracing_id — Use lineage identifiers to join across datasets (blocks → transactions → logs)
  • Use blocks-summary for analytics — Aggregate metrics endpoint reduces data transfer for dashboard queries
  • Cache function-results — Deterministic outputs are immutable; cache aggressively to reduce API calls

​
Common Patterns

Get all transactions in a block: 
{
  "chain_id": 1,
  "block_numbers": [
    12345678
  ]
}
Find logs for specific event: 
{
  "chain_id": 1,
  "topic_zeros": [
    "ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
  ],
  "from_timestamp": "2025-01-01T00:00:00Z",
  "to_timestamp": "2025-01-31T23:59:59Z"
}
Lookup contract deployment: 
{
  "chain_id": 1,
  "contract_addresses": [
    "a0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
  ]
}

​
See Also