For the complete documentation index, see llms.txt. This page is also available as Markdown.

eth_getBlockByNumber - Robinhood

Example code for the eth_getBlockByNumber JSON-RPC method. Complete guide to using the eth_getBlockByNumber JSON-RPC method in GetBlock.io Web3 documentation.

Returns block information by block number. Same response schema as eth_getBlockByHash. Use tags latest, safe, finalized, pending, earliest for relative block references. On Arbitrum Orbit, finalized means the block has settled on L1 (typically minutes behind latest).

Parameters

Parameter
Type
Required
Description

blockNumber

QUANTITY | TAG

Yes

Block number (hex) or tag (latest, safe, finalized, pending, earliest)

fullTransactions

boolean

Yes

true for full transaction objects, false for hashes only

Request Example

curl --location --request POST 'https://shared.us-east-1.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "eth_getBlockByNumber",
    "params": [
        "latest",
        false
    ],
    "id": "getblock.io"
}'
import axios from 'axios';

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "eth_getBlockByNumber",
    "params": [
        "latest",
        false
    ],
    "id": "getblock.io"
});

const config = {
    method: 'post',
    url: 'https://shared.us-east-1.getblock.io/<ACCESS-TOKEN>/',
    headers: {
        'Content-Type': 'application/json'
    },
    data: data
};

axios(config)
    .then(response => console.log(JSON.stringify(response.data, null, 2)))
    .catch(error => console.log(error));

Response Example

Response Parameters

Field
Type
Description

result

Block | null

Block object, or null if no block at this number exists

Use Cases

  • Sequential block scanning by height

  • Indexer backfill jobs

  • Block explorer pages

  • Distinguishing latest (soft-confirmed) vs finalized (L1-settled) blocks

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

-32603

Internal error

Server-side error while processing the request

429

Too Many Requests

Rate limit exceeded for your plan

SDK Integration

Last updated

Was this helpful?