GETGet blocks by version
This endpoint allows you to query transactions and block information for a specific block.
Transactions are limited by the default maximum transaction count. If not all transactions are returned, you must query the remaining transactions separately using the get transactions API. A 410 status code is returned if the block has been pruned.
The ledger version of the transaction to query for block information.
If set to true, all transactions within the block are included. If not provided, transactions are not returned.
Current block height of the chain
예: 0
Chain ID of the current chain
예: 0
Current epoch of the chain
예: 0
Oldest unpruned ledger version of the chain
예: 0
Current timestamp of the chain
예: 0
Current ledger version of the chain
예: 0
Oldest unpruned block height of the chain
예: 0
Cursor for the next page
예: string
Amount of gas actually used for transaction execution
예: 0
Represents a 64-bit unsigned integer as a string. Expressed as a string for compatibility with languages such as JavaScript that do not natively support u64 values in JSON.
A field representing the unique hash identifier of the block.
A field representing when the block was created. Provided as a UNIX timestamp in microseconds, used to track block creation order and timing. The block timestamp is used to guarantee transaction ordering and measure block creation intervals.
A field representing the version number of the first processed transaction among those included in the block. In Aptos, each transaction has a unique version number indicating the overall execution order. first_version and last_version allow you to determine the version range of transactions within the block.
A field representing the version number of the last processed transaction among those included in the block. Together with first_version, defines the version range of transactions within the block, enabling sequential lookup of all transactions in the block.
A list of all transactions included in the block.
The type of the transaction
A field representing the unique identifier of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the address of the account that sent the transaction. When expressed as a string, it is displayed as a 64-character hexadecimal string, and may be abbreviated by omitting leading zeros and adding 0x.
예: 0x1
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
예: 1234567890
A field representing the maximum amount of gas to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
예: 1000000
A field representing the gas price to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
예: 1
A field representing the transaction expiration time. Represents a 64-bit unsigned integer as a string.
예: 1634567890
The type of the payload
String representation of the Entry Function identifier defined on-chain.
예: 0x1::coin::transfer
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
예: 3,pts_1762134251280_impression_3119,0x01,0x01,Points event for user 04344295 - Type impression - Points 3,1762134251280,batch_impression_1762134251280
The type of the payload
Move script bytecode
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
예: 3,pts_1762134251280_impression_3119,0x01,0x01,Points event for user 04344295 - Type impression - Points 3,1762134251280,batch_impression_1762134251280
The type of the payload
The type of the payload
Aptos account address expressed as a hexadecimal string. This is represented as a 64-character hexadecimal string, sometimes abbreviated as a 64-character hex string with a 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
Payload that executes a single Entry Function
The type of the payload
String representation of the Entry Function identifier defined on-chain.
예: 0x1::coin::transfer
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
예: 3,pts_1762134251280_impression_3119,0x01,0x01,Points event for user 04344295 - Type impression - Points 3,1762134251280,batch_impression_1762134251280
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
Account signature scheme
The account signature scheme allows you to have two types of accounts:
A single Ed25519 key account, one private key A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction. A single Secp256k1Ecdsa key account, one private key
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
List of addresses of accounts that signed the transaction in addition to the primary signer (sender).
List of signatures from accounts that signed the transaction in addition to the primary signer (sender).
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
Account signature scheme
The account signature scheme allows you to have two types of accounts:
A single Ed25519 key account, one private key A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction. A single Secp256k1Ecdsa key account, one private key
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
List of addresses of accounts that signed the transaction in addition to the primary signer (sender).
List of signatures from accounts that signed the transaction in addition to the primary signer (sender).
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The address of the account that pays the fee.
Account signature scheme
The account signature scheme allows you to have two types of accounts:
A single Ed25519 key account, one private key A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction. A single Secp256k1Ecdsa key account, one private key
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
A field representing the nonce used to prevent transaction replay attacks. Represents a 64-bit unsigned integer as a string.
예: 590
The type of the transaction
A unique sequence ID representing the transaction version, starting from 0 and incrementing sequentially. Transaction version is used to guarantee transaction execution order and to query the state of a specific transaction.
예: 3679250756
A field representing the unique identifier of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the state change hash of the transaction, used to uniquely identify the transaction's state changes.
A field representing the event root hash of the transaction.
A field representing the state checkpoint hash of the transaction.
A field representing the amount of gas used in the transaction, used to calculate the execution cost of the transaction.
A field indicating whether the transaction succeeded; true means the transaction executed successfully, false means an error occurred during execution.
A field representing the VM status of the transaction, used to represent the execution result. Helps analyze the cause of transaction failures and troubleshoot issues.
A field representing the root hash of the accumulated transaction state.
A field representing the changes made by the transaction, used to represent the execution result.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The Move module ID is the string representation of the Move module.
Format: {address}::{module name}
address must be a 32-byte (hex) account address starting with 0x.
The module name is case-sensitive.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
The type of the change
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The deleted table data.
The type of the change
예: write_module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
The type of the change
예: write_resource
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The parsed Move resource.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
Partial data from within an account resource, displayed in JSON representation. Specifically, a map with the top-level field keys of the given resource as keys and arbitrary JSON values/objects as values.
- Move bool type: Converted to boolean.
- u8~i32: Converted to integer.
- u64~i256: Converted to string.
- address: Converted to HexEncodedBytes string (e.g. 0x1).
- Struct: Converted to object.
- vector: Converted to array.
- However, vector is converted to a HexEncodedBytes string starting with 0x.
- 0x1::string::String: Converted to regular string.
예: [object Object]
The type of the change
예: write_table_item
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A field representing the address of the account that sent the transaction. When expressed as a string, it is displayed as a 64-character hexadecimal string, and may be abbreviated by omitting leading zeros and adding 0x.
예: 0x1
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
예: 1234567890
A field representing the maximum amount of gas to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
예: 1000000
A field representing the gas price to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
예: 1
A field representing the transaction expiration time. Represents a 64-bit unsigned integer as a string.
예: 1634567890
The type of the payload
String representation of the Entry Function identifier defined on-chain.
예: 0x1::coin::transfer
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
예: 3,pts_1762134251280_impression_3119,0x01,0x01,Points event for user 04344295 - Type impression - Points 3,1762134251280,batch_impression_1762134251280
The type of the payload
Move script bytecode
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
예: 3,pts_1762134251280_impression_3119,0x01,0x01,Points event for user 04344295 - Type impression - Points 3,1762134251280,batch_impression_1762134251280
The type of the payload
The type of the payload
Aptos account address expressed as a hexadecimal string. This is represented as a 64-character hexadecimal string, sometimes abbreviated as a 64-character hex string with a 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
Payload that executes a single Entry Function
The type of the payload
String representation of the Entry Function identifier defined on-chain.
예: 0x1::coin::transfer
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
예: 3,pts_1762134251280_impression_3119,0x01,0x01,Points event for user 04344295 - Type impression - Points 3,1762134251280,batch_impression_1762134251280
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
Account signature scheme
The account signature scheme allows you to have two types of accounts:
A single Ed25519 key account, one private key A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction. A single Secp256k1Ecdsa key account, one private key
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
List of addresses of accounts that signed the transaction in addition to the primary signer (sender).
List of signatures from accounts that signed the transaction in addition to the primary signer (sender).
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
Account signature scheme
The account signature scheme allows you to have two types of accounts:
A single Ed25519 key account, one private key A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction. A single Secp256k1Ecdsa key account, one private key
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
List of addresses of accounts that signed the transaction in addition to the primary signer (sender).
List of signatures from accounts that signed the transaction in addition to the primary signer (sender).
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The address of the account that pays the fee.
Account signature scheme
The account signature scheme allows you to have two types of accounts:
A single Ed25519 key account, one private key A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction. A single Secp256k1Ecdsa key account, one private key
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
List of public keys used for the Ed25519 signature.
List of signatures mapped in the same order as the public keys.
The number of signatures required for a successful transaction.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
The type of the public key
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Public key index
Minimum number of signatures required for a successful transaction
The type of the signature
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the signature
A field representing the nonce used to prevent transaction replay attacks. Represents a 64-bit unsigned integer as a string.
예: 590
A field representing the events of the transaction.
A field representing the creation number of the event handle.
A field representing the address of the resource owner that emitted the event.
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
예: 1234567890
String representation of the Move type tag exposed in the transaction payload. Values:
boolu8u16,u32,u64,u128,u256i8,i16,i32,i64,i128,i256addresssignervector: vector<{non-reference MoveTypeId}>struct: {address}::{module_name}::{struct_name}::<{generic types}>Vector type value examples:vector<u8>vector<vector<u64>>vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>Struct type value examples:0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>0x1::account::AccountNote:
- Whitespace should be ignored when comparing two struct tag ids.
- In URL paths, it must be encoded using url-encoding (AKA percent-encoding).
A field representing the timestamp of the transaction.
The type of the transaction
A unique sequence ID representing the transaction version, starting from 0 and incrementing sequentially. Transaction version is used to guarantee transaction execution order and to query the state of a specific transaction.
예: 3679250756
A field representing the hash of the transaction.
A field representing the state change hash of the transaction.
A field representing the event root hash of the transaction.
A field representing the state checkpoint hash of the transaction.
A field representing the amount of gas used in the transaction.
A field indicating whether the transaction succeeded.
A field representing the VM status of the transaction.
A field representing the root hash of the accumulated transaction state.
A field representing the changes made by the transaction.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The Move module ID is the string representation of the Move module.
Format: {address}::{module name}
address must be a 32-byte (hex) account address starting with 0x.
The module name is case-sensitive.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
The type of the change
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The deleted table data.
The type of the change
예: write_module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
The type of the change
예: write_resource
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The parsed Move resource.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
Partial data from within an account resource, displayed in JSON representation. Specifically, a map with the top-level field keys of the given resource as keys and arbitrary JSON values/objects as values.
- Move bool type: Converted to boolean.
- u8~i32: Converted to integer.
- u64~i256: Converted to string.
- address: Converted to HexEncodedBytes string (e.g. 0x1).
- Struct: Converted to object.
- vector: Converted to array.
- However, vector is converted to a HexEncodedBytes string starting with 0x.
- 0x1::string::String: Converted to regular string.
예: [object Object]
The type of the change
예: write_table_item
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A field representing the timestamp of the transaction, used to indicate when the transaction occurred.
The type of the transaction
A unique sequence ID representing the transaction version, starting from 0 and incrementing sequentially. Transaction version is used to guarantee transaction execution order and to query the state of a specific transaction.
예: 3679250756
A field representing the unique identifier of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the state change hash of the transaction, used to uniquely identify the transaction's state changes.
A field representing the event root hash of the transaction.
A field representing the state checkpoint hash of the transaction.
A field representing the amount of gas used in the transaction, used to calculate the execution cost of the transaction.
A field indicating whether the transaction succeeded; true means the transaction executed successfully, false means an error occurred during execution.
A field representing the VM status of the transaction, used to represent the execution result. Helps analyze the cause of transaction failures and troubleshoot issues.
A field representing the root hash of the accumulated transaction state.
A field representing the changes made by the transaction, used to represent the execution result.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The Move module ID is the string representation of the Move module.
Format: {address}::{module name}
address must be a 32-byte (hex) account address starting with 0x.
The module name is case-sensitive.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
The type of the change
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The deleted table data.
The type of the change
예: write_module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
The type of the change
예: write_resource
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The parsed Move resource.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
Partial data from within an account resource, displayed in JSON representation. Specifically, a map with the top-level field keys of the given resource as keys and arbitrary JSON values/objects as values.
- Move bool type: Converted to boolean.
- u8~i32: Converted to integer.
- u64~i256: Converted to string.
- address: Converted to HexEncodedBytes string (e.g. 0x1).
- Struct: Converted to object.
- vector: Converted to array.
- However, vector is converted to a HexEncodedBytes string starting with 0x.
- 0x1::string::String: Converted to regular string.
예: [object Object]
The type of the change
예: write_table_item
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Represents the write set payload used only in genesis transactions.
The type of the payload
The type of the write set
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The Move module ID is the string representation of the Move module.
Format: {address}::{module name}
address must be a 32-byte (hex) account address starting with 0x.
The module name is case-sensitive.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
The type of the change
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The deleted table data.
The type of the change
예: write_module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The type of the change
예: write_resource
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The parsed Move resource.
The type of the change
예: write_table_item
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
예: 1234567890
String representation of the Move type tag exposed in the transaction payload. Values:
boolu8u16,u32,u64,u128,u256i8,i16,i32,i64,i128,i256addresssignervector: vector<{non-reference MoveTypeId}>struct: {address}::{module_name}::{struct_name}::<{generic types}>Vector type value examples:vector<u8>vector<vector<u64>>vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>Struct type value examples:0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>0x1::account::AccountNote:
- Whitespace should be ignored when comparing two struct tag ids.
- In URL paths, it must be encoded using url-encoding (AKA percent-encoding).
The type of the write set
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Payload which runs a script that can run multiple functions.
Move script bytecode It contains both bytecode and ABI.
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
예: 3,pts_1762134251280_impression_3119,0x01,0x01,Points event for user 04344295 - Type impression - Points 3,1762134251280,batch_impression_1762134251280
A field representing the events of the transaction.
A field representing the creation number of the event handle.
A field representing the address of the resource owner that emitted the event.
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
예: 1234567890
String representation of the Move type tag exposed in the transaction payload. Values:
boolu8u16,u32,u64,u128,u256i8,i16,i32,i64,i128,i256addresssignervector: vector<{non-reference MoveTypeId}>struct: {address}::{module_name}::{struct_name}::<{generic types}>Vector type value examples:vector<u8>vector<vector<u64>>vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>Struct type value examples:0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>0x1::account::AccountNote:
- Whitespace should be ignored when comparing two struct tag ids.
- In URL paths, it must be encoded using url-encoding (AKA percent-encoding).
A field representing the timestamp of the transaction, used to indicate when the transaction occurred.
The type of the transaction
A unique sequence ID representing the transaction version, starting from 0 and incrementing sequentially. Transaction version is used to guarantee transaction execution order and to query the state of a specific transaction.
예: 3679250756
A field representing the unique identifier of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the state change hash of the transaction, used to uniquely identify the transaction's state changes.
A field representing the event root hash of the transaction.
A field representing the state checkpoint hash of the transaction.
A field representing the amount of gas used in the transaction, used to calculate the execution cost of the transaction.
A field indicating whether the transaction succeeded; true means the transaction executed successfully, false means an error occurred during execution.
A field representing the VM status of the transaction, used to represent the execution result. Helps analyze the cause of transaction failures and troubleshoot issues.
A field representing the root hash of the accumulated transaction state.
A field representing the changes made by the transaction, used to represent the execution result.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The Move module ID is the string representation of the Move module.
Format: {address}::{module name}
address must be a 32-byte (hex) account address starting with 0x.
The module name is case-sensitive.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
The type of the change
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The deleted table data.
The type of the change
예: write_module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
The type of the change
예: write_resource
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The parsed Move resource.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
Partial data from within an account resource, displayed in JSON representation. Specifically, a map with the top-level field keys of the given resource as keys and arbitrary JSON values/objects as values.
- Move bool type: Converted to boolean.
- u8~i32: Converted to integer.
- u64~i256: Converted to string.
- address: Converted to HexEncodedBytes string (e.g. 0x1).
- Struct: Converted to object.
- vector: Converted to array.
- However, vector is converted to a HexEncodedBytes string starting with 0x.
- 0x1::string::String: Converted to regular string.
예: [object Object]
The type of the change
예: write_table_item
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A field representing the epoch of the transaction.
A field representing the round of the transaction.
A field representing the events of the transaction, used to represent the execution result.
A field representing the creation number of the event handle.
A field representing the address of the resource owner that emitted the event.
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
예: 1234567890
String representation of the Move type tag exposed in the transaction payload. Values:
boolu8u16,u32,u64,u128,u256i8,i16,i32,i64,i128,i256addresssignervector: vector<{non-reference MoveTypeId}>struct: {address}::{module_name}::{struct_name}::<{generic types}>Vector type value examples:vector<u8>vector<vector<u64>>vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>Struct type value examples:0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>0x1::account::AccountNote:
- Whitespace should be ignored when comparing two struct tag ids.
- In URL paths, it must be encoded using url-encoding (AKA percent-encoding).
A field representing the previous block votes bitvector of the transaction.
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
A field representing the failed proposer indices of the transaction.
A field representing the timestamp of the transaction, used to indicate when the transaction occurred.
A field representing the block metadata extension.
When a value exists, the internal transaction type refers to aptos_types::transaction::Transaction::BlockMetadataExt. When absent, it refers to aptos_types::transaction::Transaction::BlockMetadata.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The type of the transaction
A unique sequence ID representing the transaction version, starting from 0 and incrementing sequentially. Transaction version is used to guarantee transaction execution order and to query the state of a specific transaction.
예: 3679250756
A field representing the unique identifier of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the state change hash of the transaction, used to uniquely identify the transaction's state changes.
A field representing the event root hash of the transaction.
A field representing the state checkpoint hash of the transaction.
A field representing the amount of gas used in the transaction, used to calculate the execution cost of the transaction.
A field indicating whether the transaction succeeded; true means the transaction executed successfully, false means an error occurred during execution.
A field representing the VM status of the transaction, used to represent the execution result. Helps analyze the cause of transaction failures and troubleshoot issues.
A field representing the root hash of the accumulated transaction state.
A field representing the changes made by the transaction, used to represent the execution result.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The Move module ID is the string representation of the Move module.
Format: {address}::{module name}
address must be a 32-byte (hex) account address starting with 0x.
The module name is case-sensitive.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
The type of the change
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The deleted table data.
The type of the change
예: write_module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
The type of the change
예: write_resource
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The parsed Move resource.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
Partial data from within an account resource, displayed in JSON representation. Specifically, a map with the top-level field keys of the given resource as keys and arbitrary JSON values/objects as values.
- Move bool type: Converted to boolean.
- u8~i32: Converted to integer.
- u64~i256: Converted to string.
- address: Converted to HexEncodedBytes string (e.g. 0x1).
- Struct: Converted to object.
- vector: Converted to array.
- However, vector is converted to a HexEncodedBytes string starting with 0x.
- 0x1::string::String: Converted to regular string.
예: [object Object]
The type of the change
예: write_table_item
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A field representing the timestamp of the transaction, used to indicate when the transaction occurred.
A field representing block end information.
A field indicating whether the block gas limit was reached.
A field indicating whether the block output limit was reached.
A field representing the effective block gas units of the block.
A field representing the approximate output size of the block.
The type of the transaction
A unique sequence ID representing the transaction version, starting from 0 and incrementing sequentially. Transaction version is used to guarantee transaction execution order and to query the state of a specific transaction.
예: 3679250756
A field representing the hash of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the state change hash of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the event root hash of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the state checkpoint hash of the transaction, provided as a 64-character hexadecimal string starting with 0x.
A field representing the amount of gas used in the transaction, used to calculate the execution cost of the transaction.
A field indicating whether the transaction succeeded; true means the transaction executed successfully, false means an error occurred during execution.
A field representing the VM status of the transaction, used to represent the execution result. Helps analyze the cause of transaction failures and troubleshoot issues.
A field representing the root hash of the accumulated transaction state, provided as a 64-character hexadecimal string starting with 0x.
A field representing the changes made by the transaction, used to represent the execution result.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The Move module ID is the string representation of the Move module.
Format: {address}::{module name}
address must be a 32-byte (hex) account address starting with 0x.
The module name is case-sensitive.
The type of the change
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
The type of the change
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
The deleted table data.
The type of the change
예: write_module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A Move module
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
Friends of the module
The type of the change
예: write_resource
A 32-byte Aptos account address encoded in hexadecimal. When expressed as a string, it is a 64-character hexadecimal string. It may be abbreviated by omitting leading zeros and adding 0x prefix. For example, the address 0x0000000000000000000000000000000000000000000000000000000000000001 can be expressed as 0x1.
예: 0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1
The hash value of the state key.
The parsed Move resource.
String representation of a Move struct tag. This type exists to allow MoveStructTag to be specified as a path or query parameter (e.g. used in get_events_by_event_handle). This value is composed of:
- move_module_address, module_name, struct_name joined by two colons (::)
- Generic type parameters of the struct specified as comma-separated values Examples:
0x1::coin::CoinStore<0x1::aptos_coin::aptosCoin>0x1::account::Account
Partial data from within an account resource, displayed in JSON representation. Specifically, a map with the top-level field keys of the given resource as keys and arbitrary JSON values/objects as values.
- Move bool type: Converted to boolean.
- u8~i32: Converted to integer.
- u64~i256: Converted to string.
- address: Converted to HexEncodedBytes string (e.g. 0x1).
- Struct: Converted to object.
- vector: Converted to array.
- However, vector is converted to a HexEncodedBytes string starting with 0x.
- 0x1::string::String: Converted to regular string.
예: [object Object]
The type of the change
예: write_table_item
The hash value of the state key.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
A field representing the events of the transaction.
A field representing the creation number of the event handle.
A field representing the address of the resource owner that emitted the event.
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
예: 1234567890
String representation of the Move type tag exposed in the transaction payload. Values:
boolu8u16,u32,u64,u128,u256i8,i16,i32,i64,i128,i256addresssignervector: vector<{non-reference MoveTypeId}>struct: {address}::{module_name}::{struct_name}::<{generic types}>Vector type value examples:vector<u8>vector<vector<u64>>vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>Struct type value examples:0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>0x1::account::AccountNote:
- Whitespace should be ignored when comparing two struct tag ids.
- In URL paths, it must be encoded using url-encoding (AKA percent-encoding).
A field representing the timestamp of the transaction, used to indicate when the transaction occurred.
A field representing the quorum certified update of the transaction.
An API-friendly representation of the on-chain aptos_types::jwks::ProviderJWKs object.
An API-friendly representation of the on-chain aptos_types::aggregate_signature::AggregateSignature.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.