RPC method

eth_getBlockByNumber on Ethereum Classic

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on Ethereum Classic through the same endpoint customers use, and is re-measured weekly.

What eth_getBlockByNumber does

Returns a block by number or tag (latest, safe, finalized, pending, earliest): the header, and either the transaction hashes or the full transactions. Indexers, explorers and wallets use it to follow the chain.

eth_getBlockByNumber on Ethereum Classic: what we measured

Header fields	20
Transactions per block	0, 0, 0, 1, 4 in five consecutive blocks
Response size, full transactions (true)	2.2 KB average
Response size, hashes only (false)	1.4 KB
Gas limit	8,000,000
Gas used in the latest block	0 (0.000% of the limit)
Base fee	no baseFeePerGas field
Tag "safe"	not served (safe block not found)
Tag "finalized"	not served (finalized block not found)
Tag "pending"	block 25,527,643
Tag "earliest"	block 0

What is different on Ethereum Classic

The "safe" and "finalized" tags were not served on Ethereum Classic. Code that waits for "safe" needs a fallback, such as latest minus a confirmation count.

A real Ethereum Classic block header

From block 25,527,642, as our endpoint returned it (long hex values shortened).

{
  "number": "0x185855a",
  "hash": "0x92476c0e37d27ee9a9ec4f69ad684ce17a022a1aa30c2d24cadd6c8d7118f271",
  "parentHash": "0xf2b25ed3f1920b4abe356faa1c7e2a42fe03b392970a0cf7628da8befc9d68da",
  "nonce": "0x019a0343d459afb9",
  "mixHash": "0x59a7a78631d30cf6f1beda26fda36ac76bd600d8ebcb490fef93ee2050559afd",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "stateRoot": "0x84da2ed38c6164788f6bdaf3868a865eba42fdcf3f5b566bf99a8981500c249a",
  "miner": "0x406177b983c28eb720827985ef5953e8430d4e95",
  "difficulty": "0x6d6e5ded8e161",
  "totalDifficulty": "0x596c2c9c2503149a7e6",
  "extraData": "0xe4b883e5bda9e7a59ee4bb99e9b1bc03016ace270b25",
  "gasLimit": "0x7a1200",
  "gasUsed": "0x0",
  "timestamp": "0x6ace270b",
  "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "receiptsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "transactions": "0 transactions",
  "uncles": [],
  "size": "0x21d"
}

Example request

curl -s https://rpc.swiftnodes.io/rpc/etc?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["latest",false]}'

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/etc?key=YOUR_API_KEY"),
});

// Header plus transaction hashes (1.4 KB)
const block = await client.getBlock({ blockTag: "latest" });

// With full transactions (2.2 KB on average on Ethereum Classic)
const full = await client.getBlock({ blockNumber: block.number, includeTransactions: true });

Other methods on Ethereum Classic

eth_getBlockByNumber on other chains

Frequently asked questions

Does Ethereum Classic support eth_getBlockByNumber?

Yes. eth_getBlockByNumber answered on the SwiftNodes Ethereum Classic endpoint when our weekly probe called it through the customer path (2026-10-13).

How many transactions are in each Ethereum Classic block?

In five consecutive blocks on 2026-10-13: 0, 0, 0, 1, 4.

Ethereum Classic endpoints, live block height and WebSocket status are on the Ethereum Classic RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.