A Solana transaction can appear stuck even when the network has not yet reported its final status. Ordinary transactions use a recent blockhash, valid only for a limited time. Without checking the first transaction, pressing Send again may create a second payment.
What makes a transaction expire?
A transaction message contains a recent blockhash that ties it to a recent view of the ledger and helps prevent replay. Solana validators accept a normal blockhash only while it remains in the recent blockhash queue. Its processing-age limit is 150 slots; elapsed time varies, so do not rely on a fixed countdown.
Once the blockhash is no longer valid, a transaction that never landed can be rejected as expired. Expiry does not prove whether an earlier submission was processed. Check the signature first.
Check the original signature before retrying
- Copy the transaction signature from the wallet’s activity or confirmation screen. It is a public identifier, not your secret recovery phrase.
- Look it up on a trusted explorer set to the correct Solana cluster. Check whether it is confirmed, failed, or still unresolved.
- Compare it with wallet activity and the recipient’s history; delayed status updates can make a completed transfer look pending.
- If the transaction is confirmed, do not resend it. If it failed, read the error and decide whether the original action is still wanted.
For a normal transaction, the application that built it can also use the blockhash’s last valid block height to determine when it can no longer be processed. A timeout in an app is not by itself proof of expiry.
Why blind retries are risky
If the first transaction reached the network but the confirmation response was lost, creating a fresh transaction may send the same amount twice. A new transaction has a new message and signature, even when recipient and amount match. Before retrying, verify the original signature and whether the recipient already received the funds.
A missing confirmation is a reason to investigate the first signature—not an instruction to immediately press Send again.
When a delay is intentional
Some workflows require signing well before submission, such as offline or multi-party approvals. A standard recent blockhash may expire before everyone is ready. A Solana durable nonce uses a stored value for delayed submission. Its advance instruction must be first, and each nonce value works only once. Advancing it can invalidate a pending transaction. This advanced feature is not a general way to rescue a stuck transfer.
A safer retry checklist
- Confirm the cluster: mainnet, devnet, and testnet show different transaction histories.
- Search the original signature: use a trusted explorer or wallet history and allow for status delays.
- Check the result: distinguish a confirmed transaction from a failed or unresolved one.
- Retry deliberately: if it truly expired without processing, review the recipient, amount, and instructions again before signing a new message.
Expiry rejects stale submissions, but app delays can be confusing. Keep the signature, check the correct cluster, and replace the transaction only after understanding the original outcome. Never share a seed phrase or private key with anyone offering to “unstick” a transfer.