Get Opcodes Traces
Get the opcode traces for a historical transaction on the network with the given transaction ID or hash
Re-executes a transaction and returns a result containing detailed information for the execution, including all values from the {@code stack}, {@code memory} and {@code storage} and the entire trace of opcodes that were executed during the replay.
Note that to provide the output, the transaction needs to be re-executed on the EVM, which may take a significant amount of time to complete if stack and memory information is requested.
Transaction Id or a 32 byte hash with optional 0x prefix
{"value":"0.0.10-1234567890-000000000"}Pattern: ^(0x)?[A-Fa-f0-9]{64}|(\d{1,10})\.(\d{1,10})\.(\d{1,10})-(\d{1,19})-(\d{1,9})$If provided and set to false, stack information will not be included in the response
trueExample: trueIf provided and set to true, memory information will be included in the response
falseExample: falseIf provided and set to true, storage information will be included in the response
falseExample: falseOK
The address of the transaction recipient in hex. Zero address is set for transactions without a recipient (e.g., contract create)
Network entity ID in the format of shard.realm.num
0.0.2Pattern: ^\d{1,10}\.\d{1,10}\.\d{1,10}$Whether the transaction failed to be completely processed.
The gas used in tinybars
The returned data from the transaction in hex
Validation error
Transaction or record file not found
Too many requests
Last updated
Was this helpful?