What Is a Nonce in Solana Transactions and Why It Matters
Solana's blockhash system means transactions expire if not processed quickly. Durable nonces solve this — and understanding them explains why some transactions behave unexpectedly.

The expiry mechanism behind every Solana transaction
Every Solana transaction includes a recent blockhash — a reference to a recent block on the Solana network. This serves as a timestamp and an anti-replay mechanism. The important implication: Solana transactions expire. If a transaction is not processed within approximately 150 blocks (roughly 60–90 seconds under normal conditions), the blockhash it contains becomes too old, and the transaction is rejected as invalid. This expiry system is intentional and serves an important purpose — but it creates specific behaviors that new Solana users sometimes find confusing.
Why transactions expire and what happens when they do
The blockhash expiry prevents a class of replay attacks where an old signed transaction could be submitted to the network long after the user intended. Without expiry, a malicious party who obtained a copy of your signed transaction could submit it days or weeks later when conditions were unfavorable to you.
When a transaction expires: it simply doesn't execute. If you submitted it and it expired in the queue (common during congestion when many transactions compete for block space), you'll see a "transaction not confirmed" error in your wallet. No funds are moved. The base fee may or may not have been deducted depending on implementation. Simply resubmit with a fresh blockhash.
Durable nonces: transactions that don't expire
Some use cases require transactions that can be signed at one time but submitted later — hardware wallet signing workflows, multisig operations where multiple parties need to sign before submission, and offline transaction signing for maximum security. The Solana blockhash system makes this impossible for standard transactions.
Durable nonce accounts solve this. A durable nonce is a special account that holds a nonce value that only advances when explicitly advanced — not with each block. A transaction signed with a durable nonce remains valid until the nonce is advanced, which only happens when the transaction is submitted and processed.
For most retail token traders, durable nonces are relevant primarily as background knowledge — understanding why certain hardware wallet workflows or multisig operations work differently from standard transactions. The security properties they enable are directly relevant to understanding how serious projects manage treasury operations securely.
Always verify any token's security and authority configuration using Hannisol at Hannisol.
Ready to apply this to a real token?
Run any Solana mint address through Hannisol's 8-dimension risk engine — free, no signup required.
Analyze a token on Hannisol →

