Skip to main content

Get your own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Developers can access the debug and trace tools on the Ethereum blockchain with the following methods:

debug_traceBlockByHash

debug_traceBlockByNumber

debug_traceTransaction

debug_traceCall

trace_transaction

trace_block

Pre-built native tracers

Custom JavaScript tracers need a dedicated node

The tracers listed below are native (built-in) tracers—you select one by name, and they run on all Ethereum nodes. Custom JavaScript tracers, where you pass raw JavaScript as the tracer, are available as customized solutions on the Enterprise plan on dedicated nodes.
Developers can customize the type of tracing using various debug and trace methods, and there are numerous pre-built tracers available to choose from. Here is a list of the pre-built tracers that can be utilized:

4byteTracer

This tracer looks for function signatures that are 4 bytes long during contract execution and gathers information about the method identifiers and the size of the provided data. This information can be helpful in matching a signature against the data size.

callTracer

This tracer extracts information about all internal calls made by a transaction, providing visibility into how contracts interact with each other.

prestateTracer

This tracer returns sufficient information about an account to create a local execution of the transaction. This procedure runs the given transaction again and monitors every aspect of the state that is modified or accessed during execution.

noopTracer

This tracer does nothing but respond with a blank object. This a no operations tracer for testing setup.

flatCallTracer

This tracer returns call traces in the flat, Parity-style format—the same structure as the trace_* namespace. Instead of the nested tree produced by callTracer, it returns a flattened list of call frames, which is convenient for tooling built around the OpenEthereum/Parity trace format.
Available on Ethereum only.

muxTracer

This tracer runs several native tracers in a single pass and returns their combined output. Pass a tracerConfig object keyed by tracer name—for example, callTracer and prestateTracer, each with its own configuration—and the response is an object keyed by each tracer’s name. This avoids re-executing the transaction once per tracer.
Available on Ethereum only.

erc7562Tracer

This tracer enforces the ERC-7562 account-abstraction validation rules, tracking opcode and storage access during the validation phase of an ERC-4337 user operation. Bundlers use it to detect rule violations before a user operation enters the mempool.
Available on Ethereum only.

Custom JavaScript tracers

JavaScript-based tracers can be created through various approaches, allowing them to interact with transaction information in diverse ways. By providing a JavaScript formula along with the tracking option when employing any of the available tracking techniques, users can craft tailor-made trackers to suit their specific requirements. Find a guide to Custom JS tracing | Ethereum on the next page.
Last modified on June 22, 2026