trace_transaction on Fantom
Measured 2026-10-04 by our weekly probe, which calls trace_transaction through the same Fantom 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.
trace_transaction on Fantom: what we measured
- Default Fantom routing keeps state for roughly the last 1,000,000 blocks (about 66.3 days of Fantom history). Tracing a transaction 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/fantom?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/fantom?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: trace_transaction on Fantom
const result = await client.request({
method: "trace_transaction",
params: ["0x0000000000000000000000000000000000000000000000000000000000000000"],
});Other methods on Fantom
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallSupported
- trace_blockSupported
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
- Lisk
- Hemi
- X Layer
- BOB
Frequently asked questions
Does Fantom support trace_transaction?
Yes. trace_transaction answered correctly on the SwiftNodes Fantom endpoint in our weekly method probe (2026-10-04), which sends real requests through the customer path.
Are there limits on trace_transaction on Fantom?
Default Fantom routing keeps state for roughly the last 1,000,000 blocks (about 66.3 days of Fantom history). Tracing a transaction older than that needs historical state. Add &archive=1 to send the request to archive upstreams (paid plans).
Fantom endpoints, live block height and WebSocket status are on the Fantom RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.