RPC method

eth_getBlockByNumber on PulseChain

Supported on SwiftNodes

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

Header fields	23
Transactions per block	35, 55, 29, 40, 53 in five consecutive blocks
Response size, full transactions (true)	36.9 KB average
Response size, hashes only (false)	6.0 KB
Gas limit	44,999,957
Gas used in the latest block	4,425,537 (9.8% of the limit)
Base fee	374673 gwei
Tag "safe"	block 27,786,887
Tag "finalized"	block 27,786,855
Tag "pending"	block 27,786,940
Tag "earliest"	block 0

What is different on PulseChain

The header includes the fields added by London (EIP-1559 base fee), Shanghai (withdrawals), but not those of 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.

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

"finalized" was 83 blocks (about 14 min) behind the head.

A real PulseChain block header

From block 27,786,938, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0x154c3750082b6",
  "difficulty": "0x0",
  "extraData": "0xd883030300846765746888676f312e32342e37856c696e7578",
  "gasLimit": "0x2aea515",
  "gasUsed": "0x438741",
  "hash": "0x2e91e53e155c098b18ee92feab04ad470b5d8bc88416b2f2889ea6ebaea9e892",
  "logsBloom": "0x0020033004480020…(256 bytes)",
  "miner": "0xad33ab09bc5d1aa059697d510e5d1bc9b4adb22c",
  "mixHash": "0x2638da9649b516a2e11462e931ce1adb604f6ed6571ffc0293fa11dd0144172b",
  "nonce": "0x0000000000000000",
  "number": "0x1a7feba",
  "parentHash": "0x3df59ab31775572d2b0a56edf203cc309233b5c91786404c1ee491498701f1d8",
  "receiptsRoot": "0x12e49c6b4a221f65459de8e5688b94faaeb51e58bfe66455b4d965bbf022336c",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0x1df3",
  "stateRoot": "0x360195c668e5f924ecbf59cc505708eecba218e9afa884144d854476bef0a68a",
  "timestamp": "0x6ace2425",
  "totalDifficulty": "0xc70d815d562d3d1a955",
  "transactions": "35 transactions",
  "transactionsRoot": "0xff8e62c31fe418d0c5030c9af07235bf98806152346751774b516951b1955735",
  "uncles": [],
  "withdrawals": [
    {
      "index": "0xa10a310",
      "validatorIndex": "0x15285",
      "address": "0x639e09a40de8f423b1cffec66faedcc16d3c1265",
      "amount": "0x23df94731ea"
    },
    {
      "index": "0xa10a311",
      "validatorIndex": "0x15286",
      "address": "0x639e09a40de8f423b1cffec66faedcc16d3c1265",
      "amount": "0x23949ee0670"
    },
    "…14 more"
  ],
  "withdrawalsRoot": "0x2aa8d24f67d669381abf1a3712dbc5c5a331e66adbbfa9045485038382aef78d"
}

Example request

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

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

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

eth_getBlockByNumber on other chains

Frequently asked questions

Does PulseChain support eth_getBlockByNumber?

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

How many transactions are in each PulseChain block?

In five consecutive blocks on 2026-10-13: 35, 55, 29, 40, 53.

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

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