Documentation / New API reference / EVM

Get EVM Blocks

Reference

Last reviewed 2026-10-07

GET

https://api.taostats.io/v1/evm/blocksAPI key required

Paginated EVM blocks.

Try it

API key

Sent only to api.taostats.io, straight from your browser. It stays in this page’s memory unless you choose to remember it for this tab.

Remember for this tab

Get an API key

Parameters

Optional parameters (9)

block_number integer (int32)

Filter by exact block number.

block_start integer (int32)

Block-number range start (inclusive).

block_end integer (int32)

Block-number range end (inclusive).

timestamp_start integer (int64)

Timestamp range start, Unix seconds (inclusive).

timestamp_end integer (int64)

Timestamp range end, Unix seconds (inclusive).

page integer (int32)

Page number (1-indexed). Default: 1. Bounded window: (page − 1) × limit must be below 1,000,000. Deep OFFSET paging is linear in the offset, so an uncapped page lets one request scan tens of millions of rows; a page past the window is rejected with a 400. Reach deeper history with this endpoint's range filters (block_start/block_end, timestamp_start/timestamp_end) rather than a larger page.

limit integer (int32)

Results per page. Default: 50. Clamped into [1, 200] (out-of-range values are clamped, not rejected, matching the old API).

order_by string

Column to order by: block_number (default) or timestamp.

order_dir string

Sort direction: asc or desc. Default: desc.

Request

GET https://api.taostats.io/v1/evm/blocks

bash

curl -H "Authorization: <YOUR_API_KEY>" \
  "https://api.taostats.io/v1/evm/blocks"

const response = await fetch('https://api.taostats.io/v1/evm/blocks', {
  headers: {
    Authorization: '<YOUR_API_KEY>',
  },
});
const data = await response.json();

python

import requests

response = requests.get(
    "https://api.taostats.io/v1/evm/blocks",
    headers={"Authorization": "<YOUR_API_KEY>"},
)
data = response.json()

Parameters

Name	In	Type	Description
`block_number`	query	`integer (int32)`	Filter by exact block number.
`block_start`	query	`integer (int32)`	Block-number range start (inclusive).
`block_end`	query	`integer (int32)`	Block-number range end (inclusive).
`timestamp_start`	query	`integer (int64)`	Timestamp range start, Unix seconds (inclusive).
`timestamp_end`	query	`integer (int64)`	Timestamp range end, Unix seconds (inclusive).
`page`	query	`integer (int32)`	Page number (1-indexed). Default: 1. Bounded window: `(page − 1) × limit` must be below 1,000,000. Deep `OFFSET` paging is linear in the offset, so an uncapped `page` lets one request scan tens of millions of rows; a page past the window is rejected with a 400. Reach deeper history with this endpoint's range filters (`block_start`/`block_end`, `timestamp_start`/`timestamp_end`) rather than a larger `page`.
`limit`	query	`integer (int32)`	Results per page. Default: 50. Clamped into [1, 200] (out-of-range values are clamped, not rejected, matching the old API).
`order_by`	query	`string`	Column to order by: `block_number` (default) or `timestamp`.
`order_dir`	query	`string`	Sort direction: `asc` or `desc`. Default: `desc`.

Responses

`200` — Paginated list of EVM blocks

Field	Type	Required	Description
`data`	`array`	Yes
`data[].base_fee_per_gas`	`string`	Yes	Base fee per gas (decimal string).
`data[].difficulty`	`string`	Yes	Block difficulty (decimal string).
`data[].extra_data`	`string`	Yes	Extra data.
`data[].gas_limit`	`string`	Yes	Gas limit (decimal string).
`data[].gas_used`	`string`	Yes	Gas used (decimal string).
`data[].hash`	`string`	Yes	Block hash.
`data[].miner`	`string`	Yes	Miner address.
`data[].nonce`	`string, nullable`	Yes	Block nonce.
`data[].number`	`integer (int32)`	Yes	EVM block number.
`data[].parent_hash`	`string`	Yes	Parent block hash.
`data[].sha_3_uncles`	`string`	Yes	Uncles (sha3) hash.
`data[].size`	`integer (int32)`	Yes	Block size in bytes.
`data[].state_root`	`string`	Yes	State root hash.
`data[].timestamp`	`string`	Yes	Block time, ISO 8601 seconds precision (e.g. `2026-06-27T17:06:00Z`), matching the old API exactly.
`data[].total_difficulty`	`string`	Yes	Total chain difficulty (decimal string).
`data[].transaction_root`	`string, nullable`	Yes	Transaction trie root.
`data[].uncles`	`string, nullable`	Yes	Uncles data.
`pagination`	`object`	Yes	Pagination metadata appended to collection responses. `next_page` / `prev_page` are explicitly required+nullable in the OpenAPI spec: per `docs/api_standards.md` we emit `null` rather than omitting the field, so the SDK should model them as `Option`/nullable types that are always present in the response. `total_items` is the exact number of matching rows on every route (issue #992). It used to stop at 1,000,000, which reported a million transfers when finney holds 7,513,252 and a million events when the real figure is 981,179,110; the cap was removed on 29 Sep 2026 and nothing may reintroduce one — `crate::pagination::exact_count_sql` is the only count form, and `no_capped_count_reaches_the_api_surface` in `data-debug-scripts` fails the build if a capped one comes back. `total_pages` is still bounded, to `crate::pagination::max_reachable_page(per_page)`, because the `page` parameter is capped to a 1,000,000-row window: deep `OFFSET` paging reads every skipped row (24.7M rows / 36.6 GiB / 42 s measured on one endpoint, issue #413). So `total_pages` is exactly the last page this API will serve and `next_page` / `prev_page` stay coherent at the window edge, while `total_items` tells the caller how many rows there really are. History beyond the window is reached with each endpoint's range filters, not a larger `page`.
`pagination.current_page`	`integer (int32)`	Yes	1-indexed page that produced the rows in `data`.
`pagination.next_page`	`integer (int32), nullable`	Yes	Next page number, or `null` if this is the last page.
`pagination.per_page`	`integer (int32)`	Yes	Number of items requested per page.
`pagination.prev_page`	`integer (int32), nullable`	Yes	Previous page number, or `null` if this is the first page.
`pagination.total_items`	`integer (int64)`	Yes	Number of items matching the query across all pages. This is the exact count — every matching row, however many there are. It is not bounded by `total_pages`, so a listing can legitimately report far more items than `total_pages × per_page`.
`pagination.total_pages`	`integer (int32)`	Yes	Number of pages at the current `per_page` that this API will serve: `ceil(total_items / per_page)`, capped at `ceil(1000000 / per_page)` because the `page` parameter only reaches into the first 1,000,000 rows. When the cap bites, `total_items` is still the true total and this is the last page a request can ask for; reach deeper history with the endpoint's range filters instead of a larger `page`.

`400` — Invalid query parameter

Field	Type	Required	Description
`message`	`string`	Yes	Plain-english message describing the failure from the caller's perspective.
`status_code`	`integer (int32)`	Yes	HTTP status code (mirrored in the response status line for convenience).

`500` — Internal server error

Field	Type	Required	Description
`message`	`string`	Yes	Plain-english message describing the failure from the caller's perspective.
`status_code`	`integer (int32)`	Yes	HTTP status code (mirrored in the response status line for convenience).

Every request needs an Authorization header holding your API key — see Getting started with the Taostats API.

Was this page helpful?

Documentation / New API reference / EVM

Get EVM Blocks

Reference

Last reviewed 2026-10-07

GET

https://api.taostats.io/v1/evm/blocksAPI key required

Paginated EVM blocks.

Try it

API key

Sent only to api.taostats.io, straight from your browser. It stays in this page’s memory unless you choose to remember it for this tab.

Remember for this tab

Get an API key

Parameters

Optional parameters (9)

block_number integer (int32)

Filter by exact block number.

block_start integer (int32)

Block-number range start (inclusive).

block_end integer (int32)

Block-number range end (inclusive).

timestamp_start integer (int64)

Timestamp range start, Unix seconds (inclusive).

timestamp_end integer (int64)

Timestamp range end, Unix seconds (inclusive).

page integer (int32)

limit integer (int32)

Results per page. Default: 50. Clamped into [1, 200] (out-of-range values are clamped, not rejected, matching the old API).

order_by string

Column to order by: block_number (default) or timestamp.

order_dir string

Sort direction: asc or desc. Default: desc.

Request

GET https://api.taostats.io/v1/evm/blocks

bash

curl -H "Authorization: <YOUR_API_KEY>" \
  "https://api.taostats.io/v1/evm/blocks"

const response = await fetch('https://api.taostats.io/v1/evm/blocks', {
  headers: {
    Authorization: '<YOUR_API_KEY>',
  },
});
const data = await response.json();

python

import requests

response = requests.get(
    "https://api.taostats.io/v1/evm/blocks",
    headers={"Authorization": "<YOUR_API_KEY>"},
)
data = response.json()

Parameters

Name	In	Type	Description
`block_number`	query	`integer (int32)`	Filter by exact block number.
`block_start`	query	`integer (int32)`	Block-number range start (inclusive).
`block_end`	query	`integer (int32)`	Block-number range end (inclusive).
`timestamp_start`	query	`integer (int64)`	Timestamp range start, Unix seconds (inclusive).
`timestamp_end`	query	`integer (int64)`	Timestamp range end, Unix seconds (inclusive).
`page`	query	`integer (int32)`	Page number (1-indexed). Default: 1. Bounded window: `(page − 1) × limit` must be below 1,000,000. Deep `OFFSET` paging is linear in the offset, so an uncapped `page` lets one request scan tens of millions of rows; a page past the window is rejected with a 400. Reach deeper history with this endpoint's range filters (`block_start`/`block_end`, `timestamp_start`/`timestamp_end`) rather than a larger `page`.
`limit`	query	`integer (int32)`	Results per page. Default: 50. Clamped into [1, 200] (out-of-range values are clamped, not rejected, matching the old API).
`order_by`	query	`string`	Column to order by: `block_number` (default) or `timestamp`.
`order_dir`	query	`string`	Sort direction: `asc` or `desc`. Default: `desc`.

Responses

`200` — Paginated list of EVM blocks

Field	Type	Required	Description
`data`	`array`	Yes
`data[].base_fee_per_gas`	`string`	Yes	Base fee per gas (decimal string).
`data[].difficulty`	`string`	Yes	Block difficulty (decimal string).
`data[].extra_data`	`string`	Yes	Extra data.
`data[].gas_limit`	`string`	Yes	Gas limit (decimal string).
`data[].gas_used`	`string`	Yes	Gas used (decimal string).
`data[].hash`	`string`	Yes	Block hash.
`data[].miner`	`string`	Yes	Miner address.
`data[].nonce`	`string, nullable`	Yes	Block nonce.
`data[].number`	`integer (int32)`	Yes	EVM block number.
`data[].parent_hash`	`string`	Yes	Parent block hash.
`data[].sha_3_uncles`	`string`	Yes	Uncles (sha3) hash.
`data[].size`	`integer (int32)`	Yes	Block size in bytes.
`data[].state_root`	`string`	Yes	State root hash.
`data[].timestamp`	`string`	Yes	Block time, ISO 8601 seconds precision (e.g. `2026-06-27T17:06:00Z`), matching the old API exactly.
`data[].total_difficulty`	`string`	Yes	Total chain difficulty (decimal string).
`data[].transaction_root`	`string, nullable`	Yes	Transaction trie root.
`data[].uncles`	`string, nullable`	Yes	Uncles data.
`pagination`	`object`	Yes	Pagination metadata appended to collection responses. `next_page` / `prev_page` are explicitly required+nullable in the OpenAPI spec: per `docs/api_standards.md` we emit `null` rather than omitting the field, so the SDK should model them as `Option`/nullable types that are always present in the response. `total_items` is the exact number of matching rows on every route (issue #992). It used to stop at 1,000,000, which reported a million transfers when finney holds 7,513,252 and a million events when the real figure is 981,179,110; the cap was removed on 29 Sep 2026 and nothing may reintroduce one — `crate::pagination::exact_count_sql` is the only count form, and `no_capped_count_reaches_the_api_surface` in `data-debug-scripts` fails the build if a capped one comes back. `total_pages` is still bounded, to `crate::pagination::max_reachable_page(per_page)`, because the `page` parameter is capped to a 1,000,000-row window: deep `OFFSET` paging reads every skipped row (24.7M rows / 36.6 GiB / 42 s measured on one endpoint, issue #413). So `total_pages` is exactly the last page this API will serve and `next_page` / `prev_page` stay coherent at the window edge, while `total_items` tells the caller how many rows there really are. History beyond the window is reached with each endpoint's range filters, not a larger `page`.
`pagination.current_page`	`integer (int32)`	Yes	1-indexed page that produced the rows in `data`.
`pagination.next_page`	`integer (int32), nullable`	Yes	Next page number, or `null` if this is the last page.
`pagination.per_page`	`integer (int32)`	Yes	Number of items requested per page.
`pagination.prev_page`	`integer (int32), nullable`	Yes	Previous page number, or `null` if this is the first page.
`pagination.total_items`	`integer (int64)`	Yes	Number of items matching the query across all pages. This is the exact count — every matching row, however many there are. It is not bounded by `total_pages`, so a listing can legitimately report far more items than `total_pages × per_page`.
`pagination.total_pages`	`integer (int32)`	Yes	Number of pages at the current `per_page` that this API will serve: `ceil(total_items / per_page)`, capped at `ceil(1000000 / per_page)` because the `page` parameter only reaches into the first 1,000,000 rows. When the cap bites, `total_items` is still the true total and this is the last page a request can ask for; reach deeper history with the endpoint's range filters instead of a larger `page`.

`400` — Invalid query parameter

Field	Type	Required	Description
`message`	`string`	Yes	Plain-english message describing the failure from the caller's perspective.
`status_code`	`integer (int32)`	Yes	HTTP status code (mirrored in the response status line for convenience).

`500` — Internal server error

Field	Type	Required	Description
`message`	`string`	Yes	Plain-english message describing the failure from the caller's perspective.
`status_code`	`integer (int32)`	Yes	HTTP status code (mirrored in the response status line for convenience).

Every request needs an Authorization header holding your API key — see Getting started with the Taostats API.

Try it

Request

Parameters

Responses

200 — Paginated list of EVM blocks

400 — Invalid query parameter

500 — Internal server error

Was this page helpful?

Try it

Request

Parameters

Responses

200 — Paginated list of EVM blocks

400 — Invalid query parameter

500 — Internal server error

Was this page helpful?

`200` — Paginated list of EVM blocks

`400` — Invalid query parameter

`500` — Internal server error

`200` — Paginated list of EVM blocks

`400` — Invalid query parameter

`500` — Internal server error