As outlined in [AIP-123](https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-123-orderless-transactions.md) ([FAQ](/build/aips/aip-123)), orderless transactions execute without a sequence number. This is useful when multiple machines submit from a single sending account and the order of submission does not matter.

Replay is protected by a nonce. The blockchain stores `(sender, nonce)` pairs for committed orderless transactions from the last 60 seconds. A transaction executes only if that pair is unused, and orderless transactions expire after at most 60 seconds — shorter than sequence-number transactions.

Both accounts with an on-chain `0x1::account::Account` resource and [stateless accounts](/build/aips/aip-115) can send orderless transactions.

## Process Overview

[](#process-overview)

Orderless transactions use the extra payload fields specified in [AIP-129](https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-129-add-extra-information-in-transaction-payload.md).

1.  Build a transaction with a unique `replayProtectionNonce` (a random `u64`) and the Move entry function you want to call.
2.  Sign and submit the transaction as usual. The nonce replaces the sequence number for replay protection.

The nonce does **not** order transactions. It only ensures a transaction cannot execute twice with the same nonce before it expires.

Note

Sequence-number transactions remain the default in most SDK builders. Use orderless transactions when you need parallel submission from multiple machines — for example exchange hot wallets. See [Transaction Management](/build/guides/transaction-management) for the sequence-number model.

## TypeScript example

[](#typescript-example)

Pass `replayProtectionNonce` in the transaction `options`:

```
const transaction = await aptos.transaction.build.simple({  sender: sender.accountAddress,  data: {    function: "0x1::aptos_account::transfer",    functionArguments: [destination.accountAddress, 100],  },  options: {    replayProtectionNonce: 12345n,  },});
```

You can combine orderless replay protection with [sponsored transactions](/build/guides/sponsored-transactions) and [encrypted pending transactions](/build/guides/encrypted-pending-transactions). For how orderless transactions compose with each payment type, see [Payments](/build/guides/payments#compose-every-payment).

## SDK support

[](#sdk-support)

Each official SDK documents orderless transactions and ships a tested example:

*   [TypeScript SDK](/build/sdks/ts-sdk/building-transactions/orderless-transactions) — [`simple_orderless_transfer.ts`](https://github.com/aptos-labs/aptos-ts-sdk/blob/main/examples/typescript/simple_orderless_transfer.ts)
*   [Python SDK](/build/sdks/python-sdk/building-transactions/orderless-transactions) — [`orderless_transfer.py`](https://github.com/aptos-labs/aptos-python-sdk/blob/main/v2/examples/orderless_transfer.py)
*   [Go SDK](/build/sdks/go-sdk/building-transactions/orderless-transactions) — [`examples/orderless_transaction`](https://github.com/aptos-labs/aptos-go-sdk/tree/main/examples/orderless_transaction)
*   [Rust SDK](/build/sdks/rust-sdk/building-transactions/orderless-transactions) — [`orderless_transaction.rs`](https://github.com/aptos-labs/aptos-rust-sdk/blob/main/crates/aptos-sdk/examples/orderless_transaction.rs)