RPC method

eth_getBlockByNumber on Morph

Supported on SwiftNodes

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

Header fields	21 (1 beyond the Ethereum set)
Transactions per block	0, 1, 0, 1, 0 in five consecutive blocks
Response size, full transactions (true)	2.0 KB average
Response size, hashes only (false)	1.4 KB
Gas limit	45,000,000
Gas used in the latest block	0 (0.000% of the limit)
Base fee	0.00100 gwei
Tag "safe"	block 28,223,686
Tag "finalized"	block 28,223,087
Tag "pending"	block 28,224,066
Tag "earliest"	block 0

What is different on Morph

Morph blocks carry a field that Ethereum blocks do not. nextL1MsgIndex: specific to this chain's node software, not part of the Ethereum JSON-RPC specification. Strict schema validators need to allow it.

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

"finalized" was 977 blocks (about 31 min) behind the head.

A real Morph block header

From block 28,224,058, as our endpoint returned it (long hex values shortened).

{
  "hash": "0x47edd384382e27070be9a2e8e77eae202fd3a4a2ee353542cff7a3f7be5d11e7",
  "nextL1MsgIndex": "0x6c2f",
  "parentHash": "0xf7265572187895b519f1b65f918af89d10fe2fa047535056f6f385b61a9c1152",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "miner": "0x0000000000000000000000000000000000000000",
  "stateRoot": "0x88fc31713a1a223b65e867bbbe56a458827eeddb3b8a11d7c0f3c8b80b54d497",
  "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "receiptsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "difficulty": "0x0",
  "number": "0x1aeaa3a",
  "gasLimit": "0x2aea540",
  "gasUsed": "0x0",
  "timestamp": "0x6ace2c4d",
  "extraData": "0x",
  "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "nonce": "0x0000000000000000",
  "baseFeePerGas": "0xf4240",
  "size": "0x20b",
  "uncles": [],
  "transactions": "0 transactions"
}

Example request

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

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

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

// A block that will not be reorganised
const final = await client.getBlock({ blockTag: "finalized" });

Other methods on Morph

eth_getBlockByNumber on other chains

Frequently asked questions

Does Morph support eth_getBlockByNumber?

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

How many transactions are in each Morph block?

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

What are nextL1MsgIndex in a Morph block?

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

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

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