Get transaction by hash

Look up a transaction by its hash. This is the same hash that is returned by the API when submitting a transaction (see PendingTransaction).

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:

1. Hash message bytes: “RawTransaction” bytes + BCS bytes of Transaction.
2. Apply hash algorithm SHA3-256 to the hash message bytes.
3. Hex-encode the hash bytes with 0x prefix.

Path Parameters

txn_hash

string

required

Hash of transaction to retrieve

Response

200 - application/json

• Option 1
• Option 2
• Option 3
• Option 4
• Option 5

Enum of the different types of transactions in Aptos

expiration_timestamp_secs

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

gas_unit_price

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

hash

string

required

max_gas_amount

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

payload

object

required

An enum of the possible transaction payloads

• Option 1
• Option 2
• Option 3
• Option 4

Show child attributes

payload.arguments

any[]

required

Arguments of the function

payload.function

string

required

Entry function id is string representation of a entry function defined on-chain.

Format: {address}::{module name}::{function name}

Both module name and function name are case-sensitive.

payload.type

string

required

payload.type_arguments

string[]

required

Type arguments of the function

sender

string

required

A hex encoded 32 byte Aptos account address.

This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.

For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.

sequence_number

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

type

string

required

signature

object

An enum representing the different transaction signatures available

• Option 1
• Option 2
• Option 3

Show child attributes

signature.public_key

string

required

All bytes (Vec<u8>) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

signature.signature

string

required

All bytes (Vec<u8>) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

signature.type

string

required