Retrying still fails because the account was already locked at the first failure. Submitting the same transaction again gets rejected by nodes as a "DuplicateSignature." The key to fixing this is fetching a new recent blockhash and re-signing the transaction instead of mechanically re-sending the same one.
Understanding what "Account In Use" actually means
The Solana codebase defines the AccountInUse error clearly: "An account is currently being processed by another transaction in a way that does not support parallelism."
Think of it this way: only one transaction can operate on a particular "state" of your account at a time. Once your transaction enters the processing queue, that account becomes locked. If that first transaction fails (due to network congestion, exhausting compute units, etc.), the account may not unlock immediately.
Why does retrying fail? Solana developers have pointed this out since 2018: once a transaction throws an AccountInUse error, resending the identical transaction will only result in a DuplicateSignature error. Your transaction hash and signature have already been recorded by the network as "processing" or "failed but recorded," so resubmitting them is pointless.
Step 1: Stop blind retries and check the error code
Step 1: Confirm the error message is AccountInUse
What to do: Inspect the error details returned by your wallet or DApp.
How to do it: In wallets like Phantom or Solflare, click on the failed transaction's details and look for "Account in use" or "Transaction simulation failed: Account in use." If present, it means your account is locked by the network or the transaction has been marked as "already processed."
When you're done: You've confirmed the root cause is account contention.
Step 2: Get a new blockhash and re-sign the transaction
This is the most critical fix. Because the old transaction has been "remembered" by the network, you need a completely new transaction to supersede it.
Step 2: Refresh and resubmit the transaction
What to do: Manually refresh the transaction state in your wallet or DApp, or initiate a brand-new transaction.
How to do it:
If you're transferring within a wallet, try closing the wallet and reopening it — this usually forces the wallet to fetch the latest network state and a fresh blockhash.
If you're trading on a DApp (like Jupiter or Raydium), click "Refresh" or close the trading pair page and reopen it. The DApp will automatically generate a new transaction request.
Key point: Don't simply click "Retry." Close the current transaction window, re-enter the amount, and walk through the whole transaction flow again from scratch. That's how you generate a signature with a new
recent_blockhashand avoid theDuplicateSignatureerror.
When you're done: You've generated a transaction with a new signature and a new blockhash and successfully broadcast it.
