Alchemy provides access to an entire suite of Trace API endpoints, which give you deeper insights into transaction processing.
Endpoints
NOTE
All Trace API endpoints are only supported on Ethereum Mainnet, Sepolia and Holesky.
| Method | Description |
|---|---|
| trace_call | Executes the given call and returns a number of possible traces for it. |
| trace_block | Returns traces created at given block. |
| trace_get | Returns trace at given position. |
| trace_filter | Returns traces matching given filter. |
| trace_transaction | Returns all traces of the given transaction. |
| trace_rawTransaction | Traces a call without making the call, returning the traces. |
| trace_replayBlockTransactions | Replays all transactions in a block returning the requested traces for each transaction. |
| trace_replayTransaction | Traces a call without making the call, returning the traces. |
What exactly is the Trace API?
Is this a standard RPC endpoint, or is it something Alchemy has developed?
The Trace API is a set of non-standard RPC methods developed by the OpenEthereum team and is now maintained by the Erigon team, not by Alchemy.
See https://openethereum.github.io/JSONRPC-trace-module.
What is the difference between the Ethereum Trace API and Debug API?
The Trace API, which is supported by Erigon node clients, is equivalent to Geth's Debug API. The Debug API offers more API methods than the Trace API and is more widely used because Geth is a more popular Ethereum node client. To compare the Trace API vs. Debug API, read our API comparison guide.