See the details.
Then make your move.

What your signature authorizes

A transaction contains more than an amount and a destination. Its payload names a Move entry function, type arguments and serialized values. The envelope adds the sender, sequence number, gas price, maximum gas, expiration and chain ID. Review these details in the installed wallet before authorizing a request.

Gas, octas and the actual charge

APT uses eight decimal places. The nominal gas cap is gas-unit price multiplied by maximum gas units, expressed in octas. Actual fees depend on computation, I/O and storage effects; storage refunds can alter the net result. A maximum is a cap, while an estimate describes a projected execution. Keep a fee reserve even when sending other tokens.

The lifecycle of an Aptos transaction

Submission sends a signed transaction into the network; it is not the same as final success. Check the committed transaction response to determine what actually happened.

• Build: identify the asset, destination and exact Move call.

• Simulate: inspect expected gas, resource changes and likely errors.

• Approve: sign only after reviewing all effects.

• Submit: retain the returned public transaction hash.

• Confirm: check success, VM status, version, events and final balances.

Troubleshooting common failures

Insufficient APT may prevent execution, a stale sequence number can conflict with pending activity and a mismatched device clock can contribute to expiration errors. Check current on-chain status before resubmitting. Raising a fee does not fix a wrong asset type or an unsupported transfer function. A committed failed transaction may still have consumed gas.