RPC method

debug_traceCall on Story

Not available on SwiftNodes

Measured 2026-10-11 by our weekly probe, which calls debug_traceCall through the same Story endpoint customers use.

What debug_traceCall does

Executes a call against a block's state and returns its execution trace (with a tracer such as callTracer), without sending a transaction. It is the standard way to see what a call would do internally before you submit it.

What to use instead on Story

Story did not serve debug_traceCall in our probe. Use eth_call to see the result (but not the internal calls), or trace after the fact where trace_transaction is available.

Example request

curl -s https://rpc.swiftnodes.io/rpc/story?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"debug_traceCall","params":[{"to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest",{"tracer":"callTracer"}]}'

import { createPublicClient, http } from "viem";

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

// Any JSON-RPC method, typed loosely: debug_traceCall on Story
const result = await client.request({
  method: "debug_traceCall",
  params: [{"to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest",{"tracer":"callTracer"}],
});

Other methods on Story

debug_traceCall on other chains

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

Frequently asked questions

Does Story support debug_traceCall?

Not on our Story upstreams: debug_traceCall failed in our weekly method probe (2026-10-11). Story did not serve debug_traceCall in our probe. Use eth_call to see the result (but not the internal calls), or trace after the fact where trace_transaction is available.

Story endpoints, live block height and WebSocket status are on the Story RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.