RPC method

trace_transaction on Telos EVM

Not measured on SwiftNodes

Measured 2026-10-11 by our weekly probe, which calls trace_transaction through the same Telos EVM 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 Telos EVM

Telos EVM did not serve the trace_* namespace in our probe, which is common on OP Stack and zk chains. The debug_* namespace works on Telos EVM: use debug_traceTransaction with the callTracer instead.

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":"trace_transaction","params":["0x0000000000000000000000000000000000000000000000000000000000000000"]}'

import { createPublicClient, http } from "viem";

const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/telos?key=YOUR_API_KEY") });

// Any JSON-RPC method, typed loosely: trace_transaction on Telos EVM
const result = await client.request({
  method: "trace_transaction",
  params: ["0x0000000000000000000000000000000000000000000000000000000000000000"],
});

Other methods on Telos EVM

trace_transaction on other chains

Support differs by chain; the full measured table is on the trace_transaction reference.

Frequently asked questions

Does Telos EVM support trace_transaction?

Not on our Telos EVM upstreams: trace_transaction was not measured in our weekly method probe (2026-10-11). Telos EVM did not serve the trace_* namespace in our probe, which is common on OP Stack and zk chains. The debug_* namespace works on Telos EVM: use debug_traceTransaction with the callTracer instead.

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.