Skip to main content
POST

Overview

  • Dataset ID: 0101 - Blocks
  • Description: Aggregated block metrics (gas, throughput, fees) over a range; derived from blockdb_evm.b0101_blocks_v1. This endpoint returns aggregated buckets, not raw block rows.
  • CSV Sample: Download
  • JSON Sample: Download

Parameters

number
required
Target EVM network. See the Chain enumeration for supported values.

Range Filters (mutually exclusive)

number
Starting block number (inclusive) for the query. Use with to_block.
number
Ending block number (inclusive) for the query. Use with from_block.
string
Starting timestamp (ISO-8601). If it falls between blocks, the next block after this timestamp is used. Use with to_timestamp.
string
Ending timestamp (ISO-8601). If it falls between blocks, the last block before this timestamp is used. Use with from_timestamp.
Scoping rule: Provide exactly one of:
  1. Block range — from_block and to_block
  2. Time range — from_timestamp and to_timestamp
Do not combine scoping modes. Omitting both returns HTTP 400.

Aggregation Controls

boolean
default:"false"
Adds a 10-bucket histogram for effective gas price distribution when true.
string
default:"total"
Temporal grouping of the summary. Supported values: "total", "hour", "day".

Pagination Controls

number
default:"250"
Recommended default 250; maximum 1000 to stay under ~10 MB responses.
string
Pagination cursor from a prior call.

Response Fields

Meta

object
Echo of request metadata applied to the response.
number
EVM chain ID echoed from the request.
object
Pure echo of the window you sent (from_block/to_block/from_timestamp/to_timestamp); unset bounds are null.
object | null
The concrete window the query actually executed against, after resolving the request. For a block range on a time-bucketed endpoint (OHLC/VWAP/VWAP-aggregate/fiat VWAP), from_timestamp/to_timestamp hold the resolved timestamp window (and from_block/to_block echo your request). For a time range on a block-keyed endpoint, from_block/to_block hold the resolved block range (and the timestamps echo your request). null for selector-only requests (no window). No extra database work is done — these are the values the query already computed.
number | null
Resolved/echoed start block of the executed window.
number | null
Resolved/echoed end block of the executed window.
string | null
Resolved/echoed start timestamp (ISO-8601) of the executed window.
string | null
Resolved/echoed end timestamp (ISO-8601) of the executed window.
object
Other request knobs echoed back (fee histogram flag, bucket granularity).

Data

object[]
Buckets summarising the requested range. One element when bucket_granularity is "total".
string
ISO-8601 timestamp marking the start of the aggregation window.
string
ISO-8601 timestamp marking the end of the aggregation window.
string
Granularity echoed from the request.
number
Total number of canonical blocks in the bucket.
number
Smallest block number covered in the bucket.
number
Largest block number covered in the bucket.
number
Total transactions in the bucket.
number
Successful transactions in the bucket.
number
Failed transactions in the bucket.
number
Distinct sender addresses observed.
number
Distinct recipient addresses observed.
string
Sum of gas used (wei) across all blocks in the bucket.
string
Sum of gas limits (wei) across all blocks in the bucket.
string
Minimum base fee per gas (wei).
string
Maximum base fee per gas (wei).
string
Average base fee per gas (wei).
string
Average priority fee per gas (wei) for successful transactions. Nullable on unsupported chains.
string
Total ETH burned via base fee (wei).
string
Protocol-level issuance minus burned fees for the bucket (wei).
object[]
Ten buckets covering the 0-100 percentile range when include_fee_histogram is true.
number
Zero-based bucket index (0-9).
string
Upper bound (exclusive) of the fee bucket (wei).
number
Transactions in the fee bucket.

Envelope Fields

string | null
Pagination cursor for additional buckets when the range exceeds service limits.
number
Number of bucket elements in data.

Use Cases

  • Feed dashboards with pre-aggregated throughput metrics without ETL.
  • Detect fee regime shifts by polling hourly buckets.
  • Estimate unique user counts per epoch to complement raw transaction exports.
Last modified on July 19, 2026