Skip to content
You are reading Hyperledger Besu development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

Updated on September 24, 2020

Trace transactions

To get detailed information about transaction processing, use the TRACE API. Enable the TRACE API using the -rpc-http-api or rpc-ws-api command line options.

To specify the trace types required and retrieve the transaction traces for a block, use trace_replayBlockTransactions. Options are trace, vmTrace, or stateDiff.

To retrieve the trace type for a specific:

Your node must be an archive node (that is, synchronized without pruning or fast sync) or the requested block or transaction must be within the the number of pruning blocks retained (by default, 1024).

Important

The TRACE API is an early access feature in v1.4. The return values might change between v1.4 and v1.5.

Questions or feedback? You can discuss issues and obtain free support on Hyperledger Besu chat channel.
For Hyperledger Besu community support, contact the mailing list besu@lists.hyperledger.org