Block Operations | Ethereum

number

Returns the current chain tip's block number. Takes no operation-specific fields.

Example response:

{ "success": true, "blockNumber": 19384021 }

get

Field	Type	Required	Description
`blockNumberOrHash`	text	No (default `latest`)	A block number, block hash, or tag (`latest`, `pending`, `earliest`).
`includeTransactions`	boolean	No (default `false`)	When true, includes full transaction hashes in the block. Larger response for busy blocks.

Example response:

{
  "success": true,
  "block": {
    "number": 19384021,
    "hash": "0x8f3e...",
    "parentHash": "0x71ab...",
    "timestampUnix": 1711000000,
    "miner": "0x4838B1...",
    "gasLimit": "30000000",
    "gasUsed": "12453201",
    "transactionCount": 187,
    "transactionHashes": ["0xabc...", "0xdef..."]
  }
}

list

A composite convenience operation — fans out to N individual block.get calls under the hood rather than being a single JSON-RPC primitive.

Field	Type	Required	Description
`count`	number	No (default 10)	How many consecutive blocks to fetch. Must be between 1 and 100.
`fromBlock`	number	No	Starting block number. Omit to start from the current chain tip and work backwards.

Example response:

{
  "success": true,
  "blocks": [
    { "number": 19384021, "hash": "0x8f3e...", "...": "..." },
    { "number": 19384020, "hash": "0x71ab...", "...": "..." }
  ]
}

Cost note: block.list with a large count issues that many separate RPC calls in one node execution — keep it modest (10–20) against rate-limited free-tier provider plans. See Troubleshooting.