Look up a transaction by its hash. This is the same hash that is returned by the API when submitting a transaction
When given a transaction hash, the server first looks for the transaction in storage (on-chain, committed). If no on-chain transaction is found, it looks the transaction up by hash in the mempool (pending, not yet committed).
To create a transaction hash by yourself, do the following:
Hash message bytes: "RawTransaction" bytes + BCS bytes of Transaction.
Apply hash algorithm SHA3-256 to the hash message bytes.
Hex-encode the hash bytes with 0x prefix.
Path Parameters::
txn_hash string required
Hash of transaction to retrieve
Response Header:
X-APTOS-BLOCK-HEIGHT integer
Current block height of the chain
X-APTOS-CHAIN-ID integer
Chain ID of the current chain
X-APTOS-EPOCH integer
Current epoch of the chain
X-APTOS-LEDGER-OLDEST-VERSION integer
Oldest non-pruned ledger version of the chain
X-APTOS-LEDGER-TIMESTAMPUSEC integer
Current timestamp of the chain
X-APTOS-LEDGER-VERSION integer
Current ledger version of the chain
X-APTOS-OLDEST-BLOCK-HEIGHT integer
Oldest non-pruned block height of the chain
Response Body:
object
Type string
Hash string
sender string<hex> required
A hex encoded 32 byte Aptos account address.
sequence_number string<uint64> required
A string containing a 64-bit unsigned integer.
max_gas_amount string<uint64> required
A string containing a 64-bit unsigned integer.
gas_unit_price string<uint64> required
A string containing a 64-bit unsigned integer.
expiration_timestamp_secs string<uint64> required
A string containing a 64-bit unsigned integer.
payload object required
Payload which runs a single entry function, or
Payload which runs a script that can run multiple functions, or
An enum of the possible transaction payloads
signature object required
A single Ed25519 signature, or
A Ed25519 multi-sig signature, or
Multi agent signature for multi agent transactions