JSON-RPC Reference

debug_traceTransaction

**Availability:** Access to the `debug` namespace depends on your endpoint's method allowlist. Starting **August 4, 2026 at 12:00 PM PST**, all `debug_*` methods require an API key appended to the RPC URL — unauthenticated calls are rejected. If you receive `-32601 method not found` or `method not supported` errors, contact Conduit support to confirm your endpoint's configuration. Replays the transaction identified by `transactionHash` against the state of its parent block and returns the trace. Useful for post-hoc analysis of historical transactions (debugging reverts, building MEV analytics, etc.). For tracing hypothetical calls without an on-chain transaction, use `debug_traceCall`. Result shape depends on the `tracer` chosen in the config object. See `debug_traceCall` for the full config object schema and tracer reference. ⚡ Compute Units: [300 CU](https://docs.conduit.xyz/rpc-nodes/information/compute-units)

Request

This endpoint expects an object.
transactionHashstringRequiredformat: "^0x[0-9a-fA-F]{64}$"

32-byte hash of the transaction to replay

configobjectOptional

Trace configuration. Shared shape across all debug_trace* methods; see the TraceConfig schema.

Response

Tracer-dependent. For callTracer the result is a CallTrace object describing the outermost call and its nested sub-calls. For other tracers see the corresponding tracer documentation.

CallTraceobject

Nested call-tree entry returned by the callTracer. The top-level object describes the outermost call; each entry’s calls array contains sub-calls in execution order.

OR
map from strings to any

Non-callTracer result shape (varies by tracer).