trace_transaction on Immutable zkEVM
Measured 2026-10-11 by our weekly probe, which calls trace_transaction through the same Immutable zkEVM endpoint customers use.
What trace_transaction does
Returns the Parity-style trace of one transaction: every internal call, creation and value transfer it caused. It is the usual tool for debugging a transaction after it has been mined.
What to use instead on Immutable zkEVM
Immutable zkEVM did not serve the trace_* namespace in our probe, which is common on OP Stack and zk chains. The debug_* namespace works on Immutable zkEVM: use debug_traceTransaction with the callTracer instead.
Example request
curl -s https://rpc.swiftnodes.io/rpc/immutable-zkevm?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"trace_transaction","params":["0x0000000000000000000000000000000000000000000000000000000000000000"]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/immutable-zkevm?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: trace_transaction on Immutable zkEVM
const result = await client.request({
method: "trace_transaction",
params: ["0x0000000000000000000000000000000000000000000000000000000000000000"],
});Other methods on Immutable zkEVM
- 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_subscribeNot available
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallSupported
- trace_blockNot available
trace_transaction on other chains
Support differs by chain; the full measured table is on the trace_transaction 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
- Katana
- Ethereum Classic
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
Frequently asked questions
Does Immutable zkEVM support trace_transaction?
Not on our Immutable zkEVM upstreams: trace_transaction failed in our weekly method probe (2026-10-11). Immutable zkEVM did not serve the trace_* namespace in our probe, which is common on OP Stack and zk chains. The debug_* namespace works on Immutable zkEVM: use debug_traceTransaction with the callTracer instead.
Immutable zkEVM endpoints, live block height and WebSocket status are on the Immutable zkEVM RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.