RPC method

eth_getBlockByNumber on Abstract

Supported on SwiftNodes

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

Header fields	24 (3 beyond the Ethereum set)
Transactions per block	1, 1 in five consecutive blocks
Response size, full transactions (true)	2.5 KB average
Response size, hashes only (false)	1.5 KB
Gas limit	1,125,899,906,842,624
Gas used in the latest block	147,567
Base fee	0.0452 gwei
Tag "safe"	block 87,543,395
Tag "finalized"	block 87,474,787
Tag "pending"	not served (null)
Tag "earliest"	block 0

What is different on Abstract

Abstract blocks carry 3 fields that Ethereum blocks do not. l1BatchNumber: the L1 batch that includes the block or transaction; l1BatchTimestamp: the timestamp of the L1 batch; sealFields: consensus seal data (unused by applications). Strict schema validators need to allow them.

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.

The gas limit of 1,125,899,906,842,624 is not a real capacity figure. Abstract meters gas differently and reports a placeholder, so do not use gasUsed / gasLimit as a congestion signal there.

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

"finalized" was 71,417 blocks (about 39.5 hours) behind the head.

A real Abstract block header

From block 87,546,212, as our endpoint returned it (long hex values shortened).

{
  "baseFeePerGas": "0x2b275d0",
  "difficulty": "0x0",
  "extraData": "0x",
  "gasLimit": "0x4000000000000",
  "gasUsed": "0x2406f",
  "hash": "0x65f9673094a4c3b0edb8a0cf0f841afe48da65736341dba4772929be547b5c54",
  "l1BatchNumber": null,
  "l1BatchTimestamp": null,
  "logsBloom": "0x0000000000044000…(256 bytes)",
  "miner": "0x0000000000000000000000000000000000000000",
  "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "nonce": "0x0000000000000000",
  "number": "0x537d964",
  "parentHash": "0x9cc4facaeb91a7aab800e69972bb2be0366145c8cf3c16de0967a0cfa18b0298",
  "receiptsRoot": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "sealFields": [],
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "size": "0x0",
  "stateRoot": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "timestamp": "0x6ace2ec3",
  "totalDifficulty": "0x0",
  "transactions": "1 transactions",
  "transactionsRoot": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "uncles": []
}

Example request

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

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

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

eth_blockNumberSupported
eth_chainIdSupported
eth_getBalanceSupported
eth_getTransactionByHashSupported
eth_getTransactionReceiptSupported
eth_callSupported
eth_estimateGasNot measured
eth_gasPriceSupported
eth_maxPriorityFeePerGasSupported
eth_sendRawTransactionSupported
eth_getTransactionCountSupported
eth_getCodeSupported
eth_subscribeSupported
eth_getLogsSupported
eth_getBlockReceiptsSupported
eth_feeHistorySupported
eth_getProofNot available
eth_createAccessListNot available
debug_traceCallSupported
trace_blockNot available
trace_transactionNot available

eth_getBlockByNumber on other chains

Frequently asked questions

Does Abstract support eth_getBlockByNumber?

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

How many transactions are in each Abstract block?

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

What are l1BatchNumber and l1BatchTimestamp in a Abstract block?

l1BatchNumber is the L1 batch that includes the block or transaction. l1BatchTimestamp is the timestamp of the L1 batch.

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

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