eth_getBlockByNumber on Lisk
Everything below was measured on 2026-10-13 by calling eth_getBlockByNumber on Lisk 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 Lisk: what we measured
| Header fields | 26 |
|---|---|
| Transactions per block | 1, 1, 1, 1, 1 in five consecutive blocks |
| Response size, full transactions (true) | 2.7 KB average |
| Response size, hashes only (false) | 1.8 KB |
| Gas limit | 60,000,000 |
| Gas used in the latest block | 46,242 (0.077% of the limit) |
| Base fee | 1,015 wei |
| Tag "safe" | block 38,579,336 |
| Tag "finalized" | block 38,579,336 |
| Tag "pending" | block 38,583,884 |
| Tag "earliest" | block 0 |
What is different on Lisk
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 4,546 blocks (about 2.5 hours) behind the head.
A real Lisk block header
From block 38,583,880, as our endpoint returned it (long hex values shortened).
{
"hash": "0xa985f2121701da99ee5b2d95df1150fafede171d94886c55e843b41898dc925a",
"parentHash": "0x058d2a9e3aa384adbca8bfd0300b0d00381c7861e4e1ff583921acc12006cc0e",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"miner": "0x4200000000000000000000000000000000000011",
"stateRoot": "0x6e9ff40d785e5ab78d0ba9f8bb942c63dad0103292292979271740e9beb0cc3d",
"transactionsRoot": "0x137836d91d058a8ec3cb266a9dfe6fd3c543bfc3374c4444e9ff9b80b1a32567",
"receiptsRoot": "0x1c307bc413f8f7ea26c86f8dd1c614a3841869511f1efd1eded624d13b8c2d7d",
"logsBloom": "0x0000000000000000…(256 bytes)",
"difficulty": "0x0",
"number": "0x24cbe48",
"gasLimit": "0x3938700",
"gasUsed": "0xb4a2",
"timestamp": "0x6ace2be7",
"extraData": "0x01000003e8000000140000000000000000",
"mixHash": "0xc9cab101d3891d087af28760480fc20a100a1222daef6a4ed2e711196c90de82",
"nonce": "0x0000000000000000",
"baseFeePerGas": "0x3f7",
"withdrawalsRoot": "0xace9b06b9ec9cee66e5d648c069b59f4284b91a8db4a99c6ac88ea2781d9dc73",
"blobGasUsed": "0x0",
"excessBlobGas": "0x0",
"parentBeaconBlockRoot": "0x366bd7748968423a97b1a542f70f6bfb9b87b02c4ac5dd7c7fc0fe8756285b4e",
"requestsHash": "0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"size": "0x38c",
"uncles": [],
"transactions": "1 transactions",
"withdrawals": []
}Example request
curl -s https://rpc.swiftnodes.io/rpc/lisk?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/lisk?key=YOUR_API_KEY"),
});
// Header plus transaction hashes (1.8 KB)
const block = await client.getBlock({ blockTag: "latest" });
// With full transactions (2.7 KB on average on Lisk)
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 Lisk
- 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
- Hemi
- X Layer
- BOB
- Plasma
- Fraxtal
- 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 Lisk support eth_getBlockByNumber?
Yes. eth_getBlockByNumber answered on the SwiftNodes Lisk endpoint when our weekly probe called it through the customer path (2026-10-13).
How many transactions are in each Lisk block?
In five consecutive blocks on 2026-10-13: 1, 1, 1, 1, 1.
Lisk endpoints, live block height and WebSocket status are on the Lisk RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.