---
title: "List latest blocks across all supported EVM chains"
method: GET
path: "/v1/blocks"
tags: ["EVM Blocks"]
---

# List latest blocks across all supported EVM chains

`GET /v1/blocks`

Lists the most recent blocks from all supported EVM-compatible chains. The results can be filtered by network.

## Query parameters

- `pageToken` string
- `pageSize` integer
- `network` 'mainnet' | 'fuji' | 'testnet'

## Response `200`

Successful response

- ListEvmBlocksResponse
  - `nextPageToken` string — A token, which can be sent as `pageToken` to retrieve the next page. If this field is omitted or empty, there are no subsequent pages.
  - `blocks` EvmBlock[], required
    - `chainId` string, required — The EVM chain ID on which the block was created.
    - `blockNumber` string, required — The block number on the chain.
    - `blockTimestamp` number, required — The block creation (proposal) timestamp in seconds
    - `blockTimestampMilliseconds` number — The block creation (proposal) timestamp in milliseconds. Available only after Granite upgrade.
    - `blockMinDelayExcess` number — Minimum block delay in milliseconds. Available only after Granite upgrade.
    - `blockHash` string, required — The block hash identifier.
    - `txCount` number, required — The number of evm transactions in the block.
    - `baseFee` string, required — The base gas fee for a transaction to be included in the block.
    - `gasUsed` string, required — The gas used for transactions in the block.
    - `gasLimit` string, required — The total gas limit set for transactions in the block.
    - `gasCost` string, required
    - `parentHash` string, required — The hash of the parent block.
    - `feesSpent` string, required — The amount of fees spent/burned for transactions in the block.
    - `cumulativeTransactions` string, required — The cumulative number of transactions for the chain including this block.

## Other responses

- `400` — Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.
- `401` — When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.
- `403` — When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.
- `404` — The error is mostly returned when the client requests with either mistyped URL, or the passed resource is moved or deleted, or the resource doesn't exist.
- `429` — This error is returned when the client has sent too many, and has hit the rate limit.
- `500` — The error is a generic server side error that is returned for any uncaught and unexpected issues on the server side. This should be very rare, and you may reach out to us if the problem persists for a longer duration.
- `502` — This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.
- `503` — The error is returned for certain routes on a particular Subnet. This indicates an internal problem with our Subnet node, and may not necessarily mean the Subnet is down or affected.

---

[API](https://skmtc.net/avax/apis/data-api.md) · [All operations](https://skmtc.net/avax/apis/data-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/avax/data-api/revisions/745a94fa47f5/schema)