RPC method

eth_getBlockByNumber on MegaETH

Supported on SwiftNodes

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

Header fields	30 (4 beyond the Ethereum set)
Transactions per block	23, 23, 23, 25 in five consecutive blocks
Response size, full transactions (true)	41.5 KB average
Response size, hashes only (false)	3.5 KB
Gas limit	10,000,000,000
Gas used in the latest block	7,783,384 (0.078% of the limit)
Base fee	0.00100 gwei
Tag "safe"	block 29,099,438
Tag "finalized"	block 29,097,523
Tag "pending"	not served (null)
Tag "earliest"	block 0

What is different on MegaETH

MegaETH blocks carry 4 fields that Ethereum blocks do not. signature: the block producer's signature; miniBlockCount, miniBlockOffset, txOffset: specific to this chain's node software, not part of the Ethereum JSON-RPC specification. Strict schema validators need to allow them.

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.

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

4 of the 94 transactions in those five blocks were system transactions (4 × type 0x7e, L1-to-L2 deposit (OP Stack)). They are not user activity: filter them out when counting transactions.

The "pending" tag was not served on MegaETH. Code that waits for "pending" needs a fallback, such as latest minus a confirmation count.

"finalized" was 2,075 blocks (about 35 min) behind the head.

A real MegaETH block header

From block 29,099,593, as our endpoint returned it (long hex values shortened).

{
  "hash": "0x700e0b95ba60695ee53f371a772fd707e9337d61a440b7124e3b56b0a09bc780",
  "parentHash": "0x5da2bc89f156c970596b5b39988ce45e119b65b2978b08145093fa91041a24e1",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "miner": "0x4200000000000000000000000000000000000011",
  "stateRoot": "0x625971543f7412bea63a799dfdf3c7a5f9b5ac8186dc9374f32e66130414a705",
  "transactionsRoot": "0x28f856a3bbe356f1eac9cab4fe5411d66053005e3f9bf09415a6f9fecedc6354",
  "receiptsRoot": "0x5fe767bbb6ccdb0ab9d77326478c29cd73cd4a2de84db56baf2d9178df67756d",
  "logsBloom": "0x0000000000000100…(256 bytes)",
  "difficulty": "0x0",
  "number": "0x1bc0649",
  "gasLimit": "0x2540be400",
  "gasUsed": "0x76c3d8",
  "timestamp": "0x6ace2c1c",
  "extraData": "0x00000000fa00000001",
  "mixHash": "0x09bcee57ea882f6684006c4df2d9a5dab00d2010f39ba474fcc0ef10d0a2d2ed",
  "nonce": "0x0000000000000000",
  "baseFeePerGas": "0xf4240",
  "withdrawalsRoot": "0x69d9ba7a8bbf34bd5f307d81a9fecbfdc2eafa0d0a85a54e2eff00743f00ab02",
  "blobGasUsed": "0x0",
  "excessBlobGas": "0x0",
  "parentBeaconBlockRoot": "0xc3d8584a8eab0d06ab6fae0a2196ae858939dab89fc25d64fa551f9153293c88",
  "requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
  "size": "0x4167",
  "uncles": [],
  "transactions": "23 transactions",
  "withdrawals": [],
  "miniBlockCount": "0x63",
  "miniBlockOffset": "0xaa7d9ea6",
  "signature": "0xf0f47f81534d7880…(65 bytes)",
  "txOffset": "0x2cafaaed9"
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does MegaETH support eth_getBlockByNumber?

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

How many transactions are in each MegaETH block?

In five consecutive blocks on 2026-10-13: 23, 23, 23, 25.

What are miniBlockCount and miniBlockOffset in a MegaETH block?

miniBlockCount is not part of the Ethereum JSON-RPC specification; added by this chain's node software. miniBlockOffset is not part of the Ethereum JSON-RPC specification; added by this chain's node software.

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

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