trace_block on Katana
Measured 2026-10-11 by our weekly probe, which calls trace_block through the same Katana endpoint customers use.
What trace_block does
Returns Parity-style traces for every transaction in a block: internal calls, contract creations and value transfers. Indexers use it to reconstruct internal ETH movements that receipts do not show.
trace_block on Katana: what we measured
- Default Katana routing keeps state for roughly the last 1,000,000 blocks (about 11.6 days of Katana history). Tracing a block older than that needs historical state. Add &archive=1 to send the request to archive upstreams (paid plans).
Example request
curl -s https://rpc.swiftnodes.io/rpc/katana?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"trace_block","params":["latest"]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/katana?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: trace_block on Katana
const result = await client.request({
method: "trace_block",
params: ["latest"],
});Other methods on Katana
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getBlockByNumberSupported
- 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_transactionSupported
trace_block on other chains
Support differs by chain; the full measured table is on the trace_block reference.
- 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
- Lisk
- Hemi
- X Layer
- BOB
- Plasma
- Fraxtal
- Zora
- Story
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Ethereum Classic
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Katana support trace_block?
Yes. trace_block answered correctly on the SwiftNodes Katana endpoint in our weekly method probe (2026-10-11), which sends real requests through the customer path.
Are there limits on trace_block on Katana?
Default Katana routing keeps state for roughly the last 1,000,000 blocks (about 11.6 days of Katana history). Tracing a block older than that needs historical state. Add &archive=1 to send the request to archive upstreams (paid plans).
Katana endpoints, live block height and WebSocket status are on the Katana RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.