contracts

Get the opcode traces for a historical transaction on the network with the given transaction ID or hash

Changed on

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.

get/api/v1/contracts/results/{transactionIdOrHash}/opcodes

Request

  • Base URL
    (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /api/v1/contracts/results/{transactionIdOrHash}/opcodes
  • Auth
    none declared

Path parameters

transactionIdOrHashstring required

Transaction Id or a 32 byte hash with optional 0x prefix

Query parameters

stackboolean

If provided and set to false, stack information will not be included in the response

memoryboolean

If provided and set to true, memory information will be included in the response

storageboolean

If provided and set to true, storage information will be included in the response

Response

OK

addressstring binary required

The address of the transaction recipient in hex. Zero address is set for transactions without a recipient (e.g., contract create)

contract_idstring nullable required

Network entity ID in the format of shard.realm.num

failedboolean required

Whether the transaction failed to be completely processed.

gasinteger required

The gas used in tinybars

return_valuestring binary required

The returned data from the transaction in hex

Example response

{
  "contract_id": "0.0.2"
}

Changes

  • v14deb07b77b7dRevision changes
    • info

      the response's property default value {} was added for the status

  • v1db389f03b097Revision changes
    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property // became nullable for the status

    • breaking

      the response property // became nullable for the status

    • breaking

      the response property // became nullable for the status

    • breaking

      the response property // became nullable for the status