Arbitrum trace & debug API
C3Introspect Arbitrum execution at the opcode level. trace_*, debug_traceTransaction and call traces run on our own archive nodes, so gas profiling, MEV research and reorg analysis don't need a special add-on.
trace_* and debug_* on Arbitrum
Full trace and debug namespaces run against our Arbitrum archive nodes — call traces, state diffs and struct logs for any historic transaction.
Built for deep introspection
Profile gas, reconstruct internal calls, research MEV and reproduce reverts with accurate execution traces instead of guessing from receipts.
Frequently asked
Does Arbitrum support debug_traceTransaction?
Yes — the full debug and trace namespaces are available on our Arbitrum archive nodes.
Is tracing gated behind a premium plan?
No — trace and debug calls are metered in credits like any other method.
Top up, get a key, ship.
Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.
Get API key