Learn · Updated November 18, 2026

Durable nonce transactions, and why they break blockhash assumptions

A Solana durable nonce transaction is one whose first instruction is the System program's AdvanceNonceAccount. Its recent blockhash field then holds the value stored in a nonce account, not a recent blockhash, so it does not expire after 150 blocks. It stays valid until that nonce account is advanced, which is what makes offline signing possible.

How durable nonces work#

A nonce account is an account owned by the System program that stores three things: an authority allowed to advance it, a durable nonce value derived from a recent blockhash, and the fee rate in force when it was last advanced. To use it, the sender puts the stored value where the recent blockhash would go and makes AdvanceNonceAccount the first instruction. The transaction can be signed now and sent hours later.

When it is processed, the validator checks that the stored value matches the transaction's field, advances the nonce to a new value, and only then runs the rest. The old value can never be used again, which is how replay is prevented without a blockhash window.

Solana's documentation carries a notice that durable nonces may be deprecated in a future release; the proposal is discussed in SIMD discussion 415. As of 18 November 2026 they are in active use.

Spotting one in raw data#

CheckWhat to look for
Program of instruction 0the System program, 11111111111111111111111111111111
Instruction datastarts with the four-byte tag 04000000 (AdvanceNonceAccount)
Accounts of that instructionthe nonce account first and writable, then the RecentBlockhashes sysvar, then the nonce authority
The blockhash fieldequals the nonce value stored in that nonce account at the time

The runtime itself applies the first two checks to instruction index 0 only. An AdvanceNonceAccount anywhere else does not make the transaction a nonce transaction.

A real one from mainnet#

This v0 transaction from slot 470,901,815 succeeded and has five instructions:

PartValue
Instruction 0 programSystem program
Instruction 0 data04000000
Nonce account7L2GzhWWWbt2d2LvwAHeDP4axyZYeYDs9o37Znnxcfb1, writable
Second accountSysvarRecentB1ockHashes11111111111111111111
Nonce authoritya signer of the transaction
Blockhash fieldE17xfUfjUASaRKUBDr25kqqCPQYxh3QWNr8ZUXuLcmen, the nonce value at the time

In the two blocks we sampled, 24 transactions used a durable nonce, from 12 different fee payers and in all three formats: 6 legacy, 13 v0 and 5 v1.

What it does to expiry logic#

Anything that reasons from the recent blockhash goes wrong on a nonce transaction. Its field is not a recent blockhash, so isBlockhashValid returns false while the transaction can still land, and "the blockhash expired, so it was dropped" becomes a false conclusion. Blockhash expiry explains the normal rule; detect nonce transactions first and keep them out of it.

What does settle a nonce transaction is the nonce account. Once the stored value has moved past the one the transaction carries, the transaction can never be processed. A pipeline can read the nonce account to retire waiting nonce transactions, provided it checks the transaction's status once more after that read, since the advance may have been the transaction itself. The tested reconcile recipe does not do this yet; it keeps nonce transactions provisional until your own time limit.

When a nonce transaction fails#

The documentation separates two cases. If the nonce check itself fails, because the value is stale, the account is missing or the authority did not sign, the transaction is dropped with no fee and no state change. If the nonce check passes and an instruction then fails, the nonce is still advanced and the fee is still charged; the transaction is in the block with a failed status, and it cannot be resubmitted.

Nonce transactions in a shred pipeline#

From shreds you can detect a nonce transaction immediately, from instruction 0 alone. Flag it on the row: it changes how you retire it, it means the transaction may have been signed long before it was sent, and its blockhash field cannot be used to estimate when it was created. Everything else about decoding it is ordinary. Deduplicating transactions applies as usual, keyed on the signature.

Questions about durable nonces#

How do I tell if a Solana transaction uses a durable nonce?#

Check instruction 0: the System program with data starting 04000000, AdvanceNonceAccount.

Do durable nonce transactions expire?#

Not by blockhash. They stay valid until their nonce account is advanced, by them or by anything else.

Are durable nonces being removed?#

Solana's documentation says they may be deprecated in a future release, with the proposal under discussion. They work today.

What detection does not tell you#

Detection says the transaction uses a nonce; it does not say whether the nonce was still current when the transaction was sent, whether it landed or when it was signed. Answering any of that needs the nonce account's state or execution results, neither of which raw shreds carry.

The nonce marker is one of the instruction data patterns, a four-byte System tag, and the field it repurposes is described in what is inside a Solana transaction. To see nonce transactions in live traffic, decode a first transaction from raw shreds.

Sources#

Raw shreds on your own server

Ultra Low Latency Shreds is $200 and Standard Shreds is $100. You pay in crypto, tell us which IPv4 address and UDP port should receive the stream, and we wire it up by hand.