trace_block on Ronin

Measured 2026-10-04 by our weekly probe, which calls trace_block through the same Ronin 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.

What to use instead on Ronin

Ronin did not serve the trace_* namespace in our probe, which is common on OP Stack and zk chains. debug_traceCall did not measure as available either, so read what you can from receipts and logs, which are served.

Example request

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

// Any JSON-RPC method, typed loosely: trace_block on Ronin
const result = await client.request({
  method: "trace_block",
  params: ["latest"],
});

Other methods on Ronin

• eth_getLogsSupported
• eth_getBlockReceiptsNot measured
• eth_feeHistorySupported
• eth_getProofNot measured
• eth_createAccessListNot measured
• debug_traceCallNot measured
• trace_transactionNot available

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
• Abstract
• ApeChain
• MegaETH
• Fantom
• Lisk
• Hemi
• X Layer
• BOB

Frequently asked questions