Properties
| Name | Type | Description |
|---|---|---|
| chainId | string | The EVM chain ID on which the block was created. |
| blockNumber | string | The block number on the chain. |
| blockTimestamp | number | 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 | The block hash identifier. |
| txCount | number | The number of evm transactions in the block. |
| baseFee | string | The base gas fee for a transaction to be included in the block. |
| gasUsed | string | The gas used for transactions in the block. |
| gasLimit | string | The total gas limit set for transactions in the block. |
| gasCost | string | |
| parentHash | string | The hash of the parent block. |
| feesSpent | string | The amount of fees spent/burned for transactions in the block. |
| cumulativeTransactions | string | The cumulative number of transactions for the chain including this block. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/avalanche/main/json-schema/EvmBlock.json",
"title": "EvmBlock",
"type": "object",
"properties": {
"chainId": {
"type": "string",
"description": "The EVM chain ID on which the block was created.",
"examples": [
"43114"
]
},
"blockNumber": {
"type": "string",
"description": "The block number on the chain.",
"examples": [
"339"
]
},
"blockTimestamp": {
"type": "number",
"description": "The block creation (proposal) timestamp in seconds",
"examples": [
1648672486
]
},
"blockTimestampMilliseconds": {
"type": "number",
"description": "The block creation (proposal) timestamp in milliseconds. Available only after Granite upgrade.",
"examples": [
1648672486000
]
},
"blockMinDelayExcess": {
"type": "number",
"description": "Minimum block delay in milliseconds. Available only after Granite upgrade.",
"examples": [
7477290
]
},
"blockHash": {
"type": "string",
"description": "The block hash identifier.",
"examples": [
"0x17533aeb5193378b9ff441d61728e7a2ebaf10f61fd5310759451627dfca2e7c"
]
},
"txCount": {
"type": "number",
"description": "The number of evm transactions in the block."
},
"baseFee": {
"type": "string",
"description": "The base gas fee for a transaction to be included in the block."
},
"gasUsed": {
"type": "string",
"description": "The gas used for transactions in the block."
},
"gasLimit": {
"type": "string",
"description": "The total gas limit set for transactions in the block."
},
"gasCost": {
"type": "string"
},
"parentHash": {
"type": "string",
"description": "The hash of the parent block."
},
"feesSpent": {
"type": "string",
"description": "The amount of fees spent/burned for transactions in the block."
},
"cumulativeTransactions": {
"type": "string",
"description": "The cumulative number of transactions for the chain including this block."
}
},
"required": [
"chainId",
"blockNumber",
"blockTimestamp",
"blockHash",
"txCount",
"baseFee",
"gasUsed",
"gasLimit",
"gasCost",
"parentHash",
"feesSpent",
"cumulativeTransactions"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/EvmBlock"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.