RPC method

eth_getBlockByNumber on Blast

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on Blast 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 Blast: what we measured

Header fields	26
Transactions per block	10, 16, 14, 7, 22 in five consecutive blocks
Response size, full transactions (true)	23.2 KB average
Response size, hashes only (false)	2.3 KB
Gas limit	30,000,000
Gas used in the latest block	557,175 (1.9% of the limit)
Base fee	261 wei
Tag "safe"	block 41,542,497
Tag "finalized"	block 41,541,792
Tag "pending"	block 41,542,537
Tag "earliest"	block 0

What is different on Blast

The header includes the fields added by London (EIP-1559 base fee), Shanghai (withdrawals), Cancun (EIP-4844 blob gas), Cancun (EIP-4788 beacon root), but not those of Prague (EIP-7685 requests). Code that assumes Ethereum's current header shape must treat the missing ones as optional.

Asking for full transactions (second parameter true) made the response 10.1 times larger than hashes only. If you need only some transactions, fetch hashes and request those transactions or their receipts individually.

5 of the 69 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 743 blocks (about 25 min) behind the head.

A real Blast block header

From block 41,542,533, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0x105",
  "blobGasUsed": "0x0",
  "difficulty": "0x0",
  "excessBlobGas": "0x0",
  "extraData": "0x",
  "gasLimit": "0x1c9c380",
  "gasUsed": "0x88077",
  "hash": "0x53e7f1b7c92b01eaba2a92d7715914525c591b78b23049a9b8c65003b42fe5c9",
  "logsBloom": "0x0000000000004000…(256 bytes)",
  "miner": "0x4200000000000000000000000000000000000011",
  "mixHash": "0x5e210176728478aeba209846f08fac60955c53bb8085ade92e818e0fdf7a8df8",
  "nonce": "0x0000000000000000",
  "number": "0x279e385",
  "parentBeaconBlockRoot": "0x49a3bd14cea8f9d0d72991501ab41d824ba5954efe4deeaf9e85ffcc0e62eb63",
  "parentHash": "0xb3c360a0599e0d995b88f537a382dbc8858cdaf81a9a9d404f37f7bfd609045c",
  "receiptsRoot": "0x913b9eb538d2b4c2a49e2a2e98c6da0a39882437bb1e1e19b922cfc1280593b8",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0xd94",
  "stateRoot": "0x15fb1239ba0b8dd58a6428c5608666323f99777aa77ffc046fbf6aeb86e3b628",
  "timestamp": "0x6ace2561",
  "totalDifficulty": "0x0",
  "transactions": "10 transactions",
  "transactionsRoot": "0xf9cbba9be91d70febb97655c92d0290b0e93aa045107fc128a0c0e822f53edc2",
  "uncles": [],
  "withdrawals": [],
  "withdrawalsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421"
}

Example request

curl -s https://rpc.swiftnodes.io/rpc/blast?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/blast?key=YOUR_API_KEY"),
});

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

// With full transactions (23.2 KB on average on Blast)
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 Blast

eth_getBlockByNumber on other chains

Frequently asked questions

Does Blast support eth_getBlockByNumber?

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

How many transactions are in each Blast block?

In five consecutive blocks on 2026-10-13: 10, 16, 14, 7, 22.

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

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