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

eth_getBlockByNumber - Bittensor

Example code for the eth_getBlockByNumber JSON-RPC method. Complete guide on how to use eth_getBlockByNumber JSON-RPC in GetBlock Web3 documentation.

Returns EVM block info by block number. Use tags latest, safe, finalized, or earliest for relative references. Pass true as the second parameter for full transaction objects; false for hashes only.

Subtensor EVM JSON-RPC method. Call against a GetBlock endpoint configured for the EVM interface (not the Substrate interface). Subtensor EVM uses chain ID 945 (0x3b1). Standard Ethereum tooling — ethers.js, viem, Hardhat, Foundry, MetaMask — works unmodified.

Parameters

Parameter
Type
Required
Description

blockNumber

QUANTITY | TAG

Yes

Block number (hex) or tag

fullTransactions

boolean

Yes

true for full transaction objects, false for hashes only

Request Example

curl --location --request POST 'https://go.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://go.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

EVM block object, or null if no block at this number

result.number

QUANTITY

Block number

result.hash

DATA

Block hash

result.transactions

array

Transaction hashes (or full objects if requested)

Use Cases

  • EVM block scanning

  • Indexer backfill jobs

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

-32601

Method not found

Method does not exist on this interface — check whether you're calling a Substrate method on an EVM endpoint or vice versa

-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?