POSTtx
https://near-mainnet.nodit.io/Returns a transaction's execution status and result, looked up by transaction hash and signer account.
tx is the method for checking the status of a transaction you have already sent. The tx_status and broadcast_tx_sync methods are not available. Specify tx_hash together with sender_account_id (the transaction signer); instead of tx_hash, you can also pass the signed transaction itself as signed_tx_base64. If wait_until is omitted, the call waits until the transaction reaches EXECUTED_OPTIMISTIC. With NONE, it returns the current status immediately without waiting. The node waits up to 10 seconds for the requested milestone and returns TIMEOUT_ERROR if it is not reached in time. If the node has no record of the transaction, it returns UNKNOWN_TRANSACTION.
Request ID. Any string; it is returned unchanged in the response.
Base58-encoded 32-byte hash (block hash, chunk hash, transaction hash, etc.).
NEAR account ID. A human-readable name (e.g. wrap.near) or a 64-character hex implicit account ID.
The execution milestone to wait for before returning a response. Defaults to EXECUTED_OPTIMISTIC. Each value further down is a later milestone.
NONE: The transaction is waiting to be included in a block.INCLUDED: The transaction is included in a block (the block may not be finalized yet).EXECUTED_OPTIMISTIC: Included in a block, and all non-refund receipts have executed (the blocks may not be finalized yet).INCLUDED_FINAL: The transaction is included in a finalized block.EXECUTED: Included in a finalized block, and all non-refund receipts have executed.FINAL: Included in a finalized block, and all receipts, including refunds, are finalized.
JSON-RPC version
Request ID
The execution milestone the transaction has reached. Values have the same meaning as the wait_until request parameter.
The final execution result of the transaction. On success it contains SuccessValue (the base64-encoded return value, or an empty string if nothing is returned); on failure it contains Failure (an object describing the cause). It is the string NotStarted if the transaction has not yet been converted to a receipt, and Started while execution is in progress.
The signed transaction as submitted.
NEAR account ID. A human-readable name (e.g. wrap.near) or a 64-character hex implicit account ID.
Example: wrap.near
Base58-encoded public key prefixed with ed25519: or secp256k1:.
Example: ed25519:168vdqFUxij2yvsxYgAGoykJMX7tgrPKVCH484A8nHP
The nonce of the access key used for signing.
NEAR account ID. A human-readable name (e.g. wrap.near) or a 64-character hex implicit account ID.
Example: wrap.near
The actions in the transaction. Each item is an object keyed by the action name, or a string such as CreateAccount. The action name is one of CreateAccount, DeployContract, FunctionCall, Transfer, Stake, AddKey, DeleteKey, DeleteAccount, Delegate, DelegateV2, DeployGlobalContract, DeployGlobalContractByAccountId, UseGlobalContract, UseGlobalContractByAccountId, DeterministicStateInit, TransferToGasKey, WithdrawFromGasKey, UniversalStateInit.
Deprecated; retained for backward compatibility.
Transaction signature (base58 with an ed25519: or secp256k1: prefix)
Base58-encoded 32-byte hash (block hash, chunk hash, transaction hash, etc.).
Example: 8EjuQRnAJiWkRmqxfexQFJWXXonuSMbz5AZziJLCWnWS
The execution outcome of the transaction itself. The transaction is converted to the first receipt, and id is the transaction hash.
Base58-encoded 32-byte hash (block hash, chunk hash, transaction hash, etc.).
Example: 8EjuQRnAJiWkRmqxfexQFJWXXonuSMbz5AZziJLCWnWS
Base58-encoded 32-byte hash (block hash, chunk hash, transaction hash, etc.).
Example: 8EjuQRnAJiWkRmqxfexQFJWXXonuSMbz5AZziJLCWnWS
The execution outcome of the transaction.
The account ID where execution took place: signer_id for a transaction, the receiver account for a receipt.
The amount of gas burnt by the execution.
The amount of tokens burnt for the gas used (yoctoNEAR, decimal string)
Logs emitted during execution. NEP standard events are JSON strings prefixed with EVENT_JSON:.
IDs of the receipts generated by this execution.
Execution status. On success it contains SuccessValue (the base64-encoded return value) or SuccessReceiptId (the ID of the generated receipt); on failure it contains Failure (an object describing the cause). It is the string Unknown when the result is not known.
Versioned execution metadata. Contains version, gas_profile (gas used per cost item), and contracts (version 4 and later: for each action, the contract attached to the receiver account just before the action ran).
The Merkle path that verifies the outcome against the block's outcome root. Each item has a hash and a direction (Left or Right).
Execution outcomes of the receipts that followed from the transaction. Each item's id is a receipt ID, and the structure is the same as transaction_outcome.
Base58-encoded 32-byte hash (block hash, chunk hash, transaction hash, etc.).
Example: 8EjuQRnAJiWkRmqxfexQFJWXXonuSMbz5AZziJLCWnWS
Base58-encoded 32-byte hash (block hash, chunk hash, transaction hash, etc.).
Example: 8EjuQRnAJiWkRmqxfexQFJWXXonuSMbz5AZziJLCWnWS
The execution outcome of the receipt.
The account ID where execution took place: signer_id for a transaction, the receiver account for a receipt.
The amount of gas burnt by the execution.
The amount of tokens burnt for the gas used (yoctoNEAR, decimal string)
Logs emitted during execution. NEP standard events are JSON strings prefixed with EVENT_JSON:.
IDs of the receipts generated by this execution.
Execution status. On success it contains SuccessValue (the base64-encoded return value) or SuccessReceiptId (the ID of the generated receipt); on failure it contains Failure (an object describing the cause). It is the string Unknown when the result is not known.
Versioned execution metadata. Contains version, gas_profile (gas used per cost item), and contracts (version 4 and later: for each action, the contract attached to the receiver account just before the action ran).
The Merkle path that verifies the outcome against the block's outcome root. Each item has a hash and a direction (Left or Right).
Error class. REQUEST_VALIDATION_ERROR (invalid request), HANDLER_ERROR (processing error), INTERNAL_ERROR (node internal error)
The specific cause of the error.
Name of the error cause (e.g. UNKNOWN_BLOCK, UNKNOWN_ACCOUNT, PARSE_ERROR)
Additional information about the error (block hash, height, account ID, etc.)
Legacy JSON-RPC error code (e.g. -32000 server error, -32700 parse error, -32601 method not found)
Legacy error message
Legacy error details