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.
Last update: March 17, 2022

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.

The TRACE API has two sets of trace calls, ad-hoc tracing APIs and transaction-trace filtering APIs.

Ad-hoc tracing APIs

These APIs allow different diagnostic options when tracing calls or transactions. The options are trace, vmTrace, or stateDiff.

To use the ad-hoc tracing APIs, the requested block or transaction must be within the number of blocks retained with pruning enabled (by default, 1024).

The ad-hoc tracing APIs are:

Transaction-trace filtering APIs

These APIs allow you to filter and search by specific information such as the block, address, or transaction. These APIs only use the trace type.

To use the transaction-trace filtering APIs, 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 number of blocks retained with pruning enabled (by default, 1024).

The transaction-trace filtering APIs are:

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