Nonce
Nonce retrieves the next transaction sequence number (nonce) of an address so you can build transactions in the correct order. You can retrieve the transaction count of an address with the RPC API, or retrieve the next nonce directly with the Data API.
If the nonce is wrong, the transaction is rejected or stays pending, and when one transaction is pending, later transactions from the same address are not processed either. For institutional wallets with a high volume of withdrawals, accurate nonce management directly determines withdrawal throughput.
Use Cases
- Withdrawal OpsFix the nonce right before a withdrawal
Retrieve the pending-based nonce immediately before the signing request and include it in the transaction. This prevents transactions from being rejected because the nonce is already used.
- EngineeringManage order for parallel withdrawals
When you submit multiple transactions at the same time, reserve nonces in your application to keep the order. This prevents nonce conflicts that cause transactions to be rejected or to delay each other.
- InfrastructureOperate separate withdrawal addresses
Split withdrawals across multiple addresses so that a pending transaction on one address does not delay all withdrawals. Combined with multi-address lookup APIs such as Get Transactions by Accounts ([Activity](/wallet-node/activity)), you can also keep the reconciliation workload manageable.