SwiftNodesSwiftNodes
Sign In
RPC method

eth_getBlockByNumber on Telos EVM

Supported on SwiftNodes

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

Header fields20
Transactions per block0, 0, 0, 0, 0 in five consecutive blocks
Response size, full transactions (true)1.4 KB average
Response size, hashes only (false)40 bytes
Gas limit2,147,483,647
Gas used in the latest block0 (0.000% of the limit)
Base feeno baseFeePerGas field
Tag "safe"block 493,749,276
Tag "finalized"block 493,749,328
Tag "pending"block 493,749,333
Tag "earliest"block 0

What is different on Telos EVM

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

A real Telos EVM block header

From block 493,749,307, as our endpoint returned it (long hex values shortened).

{
  "hash": "0xe2d3fee189eda32cb247f589575324266cb87a259ff53ed1bec880f5b713771a",
  "parentHash": "0xd42bba0b7589986d6a1cd955889fd17b3bbd1471b834f025db6ab6edcc446987",
  "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  "miner": "0x0000000000000000000000000000000000000000",
  "stateRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "receiptsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "difficulty": "0x0",
  "number": "0x1d6e043b",
  "gasLimit": "0x7fffffff",
  "gasUsed": "0x0",
  "timestamp": "0x6ace2e89",
  "totalDifficulty": "0x0",
  "extraData": "0x1d6e045fcbfded9e293aa86b047e4f75b5ef51cd1d349fd17e259bb4093ce166",
  "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "nonce": "0x0000000000000000",
  "uncles": [],
  "transactions": "0 transactions",
  "size": "0x221"
}

Example request

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

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

// With full transactions (1.4 KB on average on Telos EVM)
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 Telos EVM

eth_getBlockByNumber on other chains

Frequently asked questions

Does Telos EVM support eth_getBlockByNumber?

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

How many transactions are in each Telos EVM block?

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

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

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