POSTSimulate transaction
API that simulates a transaction without actually executing it.
The simulation result includes the same transaction output and events as when executing an actual signed transaction. However, the state hash is not included because storage is not updated. You can use this API to estimate the maximum gas amount required when submitting a transaction.
How to use:
- Create a transaction with zero-padded signatures.
- Submit the created transaction to this API.
To use this endpoint in BCS format, you must submit a signed transaction encoded in BCS.
When set to True, the transaction's gas unit price is ignored and the estimated value is used.
When set to True, the transaction's max gas amount is ignored and the estimated value is used.
When set to True, the transaction is executed at a higher price than the estimate.
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.
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
A field representing the maximum amount of gas to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
A field representing the gas price to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
A field representing the transaction expiration time. Represents a 64-bit unsigned integer as a string.
A field representing the payload to use when the transaction occurs.
The type of the payload
String representation of the Entry Function identifier defined on-chain.
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
A field representing the nonce used to prevent transaction replay attacks. Represents a 64-bit unsigned integer as a string.
A field representing the transaction signature. One of Ed25519, MultiEd25519, MultiAgent, FeePayer, Account, or NoAccount can be selected.
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.
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
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
Whether the struct is an event struct
Whether the struct is an enum
Ability associated with the Move struct
Generic type parameters associated with the Move function.
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
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.
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
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.
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
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.
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
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.
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
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.
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