eth_getBlockByNumber on Fraxtal
Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on Fraxtal 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 Fraxtal: what we measured
| Header fields | 26 |
|---|---|
| Transactions per block | 1, 1, 1, 1, 1 in five consecutive blocks |
| Response size, full transactions (true) | 2.6 KB average |
| Response size, hashes only (false) | 1.8 KB |
| Gas limit | 30,000,000 |
| Gas used in the latest block | 48,367 (0.161% of the limit) |
| Base fee | 254 wei |
| Tag "safe" | block 42,542,158 |
| Tag "finalized" | block 42,541,615 |
| Tag "pending" | block 42,542,217 |
| Tag "earliest" | block 0 |
What is different on Fraxtal
The header includes the fields added by London (EIP-1559 base fee), Shanghai (withdrawals), Cancun (EIP-4844 blob gas), Cancun (EIP-4788 beacon root), Prague (EIP-7685 requests). Code that assumes Ethereum's current header shape will parse it as is.
5 of the 5 transactions in those five blocks were system transactions (5 × type 0x7e, L1-to-L2 deposit (OP Stack)). They are not user activity: filter them out when counting transactions.
"finalized" was 601 blocks (about 20 min) behind the head.
A real Fraxtal block header
From block 42,542,213, as our endpoint returned it (long hex values shortened).
{
"hash": "0x400448d438d5338492fa85e53483f4671e579b32b7d59b7c1c4c4bbb05412230",
"parentHash": "0xd915806cbb5b4e9bb7b984544a4f72817affefdc11ae14011d15fe51800fa2bf",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"miner": "0x4200000000000000000000000000000000000011",
"stateRoot": "0x01d73302a95b1d60cae3dac73921b447a3f2032e4c40c647fc96fdcc36574cbe",
"transactionsRoot": "0x37e301dc40ec017b03d6457ad902cc976c408d81f8b8824107a146f287dbff88",
"receiptsRoot": "0x4d93aa1ee1e913788817c3d9e7a4364d74c5f0c038d650cb6e0c272904dd7e05",
"logsBloom": "0x0000000000000000…(256 bytes)",
"difficulty": "0x0",
"number": "0x2892485",
"gasLimit": "0x1c9c380",
"gasUsed": "0xbcef",
"timestamp": "0x6ace2661",
"extraData": "0x00000000fa0000000a",
"mixHash": "0x59ef452e9e5c9ea841d12194d2fa1b767b3e76a3357bf32287e048d749f94552",
"nonce": "0x0000000000000000",
"baseFeePerGas": "0xfe",
"withdrawalsRoot": "0xfe98a2d72d7bcd1032efd1428e1029b4f0017761f6d6c9c72c70e784035a1e11",
"blobGasUsed": "0x0",
"excessBlobGas": "0x0",
"parentBeaconBlockRoot": "0xaeb58f112727329bbb98c90e9d952bb9338c37a840c27397d51256bf729db66b",
"requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"size": "0x381",
"uncles": [],
"transactions": "1 transactions",
"withdrawals": []
}Example request
curl -s https://rpc.swiftnodes.io/rpc/fraxtal?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/fraxtal?key=YOUR_API_KEY"),
});
// Header plus transaction hashes (1.8 KB)
const block = await client.getBlock({ blockTag: "latest" });
// With full transactions (2.6 KB on average on Fraxtal)
const full = await client.getBlock({ blockNumber: block.number, includeTransactions: true });
const userTxs = full.transactions.filter((t) => !["0x7e"].includes(t.typeHex));
// A block that will not be reorganised
const final = await client.getBlock({ blockTag: "finalized" });Other methods on Fraxtal
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getTransactionByHashSupported
- eth_getTransactionReceiptSupported
- eth_callSupported
- eth_estimateGasSupported
- eth_gasPriceSupported
- eth_maxPriorityFeePerGasSupported
- eth_sendRawTransactionSupported
- eth_getTransactionCountSupported
- eth_getCodeSupported
- eth_subscribeSupported
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallSupported
- trace_blockSupported
- trace_transactionSupported
eth_getBlockByNumber on other chains
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- BNB Smart Chain
- Avalanche
- Sonic
- Linea
- Scroll
- zkSync Era
- Blast
- Mantle
- Gnosis
- Celo
- Berachain
- Monad
- Unichain
- Kaia
- PulseChain
- World Chain
- Ronin
- Abstract
- ApeChain
- MegaETH
- Fantom
- Lisk
- Hemi
- X Layer
- BOB
- Plasma
- Zora
- Story
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Katana
- Ethereum Classic
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Fraxtal support eth_getBlockByNumber?
Yes. eth_getBlockByNumber answered on the SwiftNodes Fraxtal endpoint when our weekly probe called it through the customer path (2026-10-13).
How many transactions are in each Fraxtal block?
In five consecutive blocks on 2026-10-13: 1, 1, 1, 1, 1.
Fraxtal endpoints, live block height and WebSocket status are on the Fraxtal RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.