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 with the following methods:

debug_traceBlockByHash

debug_traceBlockByNumber

debug_traceCall

debug_traceTransaction

​
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. 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. Further 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.
Last modified on June 22, 2026