Do not resend immediately. First save the transaction signature, check its on-chain status, and read any execution error. A successful sendTransaction response only means an RPC server accepted and relayed your signed transaction; it does not prove that the Solana cluster processed or confirmed it. Once you know whether the transaction is pending, expired, or failed, you can choose the safe remedy: wait, rebuild with a fresh blockhash, correct a balance or token-account problem, adjust fees, or investigate your RPC endpoint.
Start with the signature, not the send response
Every submitted Solana transaction has a signature (often called a transaction ID). Copy it from the wallet, application log, or RPC response before taking any other action. It is the identifier you need to determine whether an attempted payment, swap, vote, or contract interaction already reached the cluster.
As an Amazon Associate I earn from qualifying purchases.
The JSON-RPC sendTransaction method performs transaction encoding, signature verification, and preflight simulation unless the caller changes those settings. Its response is still only an acknowledgement from the RPC path. Solana’s documentation explicitly warns that a successful response does not guarantee processing or confirmation by the cluster.
Check the status directly
Query the signature with getSignatureStatuses through the same wallet or a healthy RPC endpoint. A typical request is:
#1 Best Overall
- EAL5+ CERTIFIED SECURE ELEMENT + FINGERPRINT PROTECTION — Your private keys stay encrypted offline on a certified EAL5+ chip, the same security tier used in EMV bank cards. Built by DCENT, securing crypto since 2018. Fingerprint authentication adds a second layer no PIN-only wallet can match.
- 10,000+ ASSETS NATIVE ON 100+ BLOCKCHAINS — Hold Bitcoin, Ethereum, XRP, Solana, Cardano, popular stablecoins (USDT, USDC), and NFTs in one wallet. No third-party apps, no fragmented setup — every supported asset works straight out of the box.
- TAP-TO-SIGN MOBILE EXPERIENCE — Pair your wallet with the DCENT mobile app over Bluetooth. Manage tokens, review transactions, and access in-app swap features directly from your phone — no cables, no desktop required.
- WEB3 & dAPP ACCESS VIA METAMASK — Connect to MetaMask and other browser extension wallets to manage NFTs, claim airdrops, and access dApps. A large screen and intuitive 4-button interface keep every transaction clearly visible before you sign.
- SEAMLESS FIRMWARE UPDATES & 30-DAY MONEY-BACK GUARANTEE — Apply security updates without resetting your wallet or migrating funds. Backed by Amazon's 30-day money-back guarantee — your purchase is risk-free.
{"jsonrpc":"2.0","id":1,"method":"getSignatureStatuses","params":[["YOUR_SIGNATURE"],{"searchTransactionHistory":true}]}The result can show a confirmation state such as processed, confirmed, or finalized, plus an err value. A null status means that endpoint cannot currently find the signature; it does not by itself prove that the transaction never landed. Check again using a healthy endpoint and inspect the transaction in Solana Explorer when appropriate.
- No status yet: wait briefly, then query again. Verify that your endpoint is current and that the transaction’s recent-blockhash validity window has not closed.
- Status with an error: treat the transaction as failed. Read the specific simulation or execution error before constructing a replacement.
- Processed or confirmed: do not submit an identical payment merely because your application screen has not refreshed. Check the recipient, amount, and desired commitment level.
- Finalized: the transaction has reached the strongest commonly used confirmation level; record the signature for your records.
“Solana transaction pending” or “stuck”: decide whether to wait
A pending transaction may be moving through the cluster, waiting behind other work, or invisible because your RPC node is behind. Solana has no universal guaranteed wait time, and current congestion, endpoint health, transaction size, compute demand, and fee conditions vary.
- Keep the original signature and note when it was submitted.
- Query
getSignatureStatusesagain through a second healthy endpoint if the first returns null or stale information. - Compare the current slot and blockhash information from the endpoint. A lagging node can make a landed transaction appear absent.
- Inspect the validity of the recent blockhash used by the original transaction. Recent blockhashes are time-limited; the maximum recent-blockhash processing age documented by Solana is 150 slots.
- If the signature later appears, use that result rather than creating a duplicate action.
Do not blindly resend a payment while the original signature is unresolved. Two copies could both execute if the first transaction is merely delayed. For a transfer, that can mean paying twice; for a swap or other state-changing instruction, the second attempt can have a different market result.
“Solana transaction failed”: read the error before retrying
Solana transactions are atomic. If any instruction fails, the entire transaction fails and all state changes from that transaction are reverted. The transaction fee is still charged, however, because the network consumed resources to process the attempt.
Expired or unrecognized blockhash
A recent blockhash prevents indefinite replay and gives a transaction a limited processing window. If the error indicates that the blockhash is expired, not found, or otherwise invalid, the signed bytes cannot be repaired. Fetch a fresh blockhash, rebuild the transaction with the same intended instructions, and sign it again.
Rank #2
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
Before doing so, query the original signature. An endpoint can report a blockhash-related submission problem even while another path is catching up. Confirming that the original did not land protects you from duplicating a payment or contract action.
Insufficient SOL for fees
Every Solana transaction requires a fee paid in SOL. The fee payer must hold enough SOL for the base fee and any optional prioritization fee. Having enough tokens for a transfer does not guarantee that the fee payer has enough SOL. Add the required SOL to the fee-paying account, then create and sign a new transaction.
Free tools Windows power users keep installed
One-click scans. No signup required.
The documented base fee is 5,000 lamports per signature. This is a protocol fee parameter, not a promise that your total cost will always equal that amount: transactions can contain multiple signatures and an optional prioritization component.
Insufficient token balance
A token transfer or program instruction can fail when the source account lacks the required token amount, including any amount needed for fees charged by the token program or application. Check the exact mint and token-account balance, not just the wallet’s headline token total. Correct the amount or fund the source account, then rebuild the transaction.
Missing associated token account
If the destination has no token account for the relevant mint, a transfer may fail. The sender or application must create the appropriate associated token account, ensure the payer can cover its rent-related account cost where applicable, and then submit the transfer. Simply resending unchanged, invalid instructions will produce the same error.
Rank #3
- 【Military‑grade EAL6+ security&Easy to Use】Safnect crypto wallet eatures the top-tier EAL6+ security technology and a sealed secure-element chip — No Bluetooth. No Wi‑Fi. No battery. No seed phrase to manage. Your cryptocurrencies stay strongly protected from online attackers, it is immune to remote hacks and effortless for first-time users.
- 【3-Pack Backup = Double Secure】This 100% offline hardware wallet not just a 3‑pack. It's a breakthrough in key management.You can store these three cold crypto wallets in separate locations for safer, decentralized asset protection.
- 【Instant Tap Connection&Friendly for Begginer】Simply tap the crypto wallet card against your mobile device to pair with the Safnect App in seconds. Effortlessly buy, sell and transfer crypto assets safely through the app. Experience the fast convenience of a hot wallet, paired with the robust security of genuine cold storage.
- 【Multi-Chain & Multi-Account Management】 The Safnect cold crypto wallet seamlessly manages Bitcoin, Ethereum, Solana, and over 2,800 tokens across 54+ mainstream blockchains, giving you complete multi-chain and multi-account control.You can buy, sell, swap, stake, and spend cryptocurrency directly any time any way.
- 【Basically Indestructible&Easy to Carry】Only 2 mm thin with a credit-card sized design, this crypto wallet features IP66 waterproofing and bend-resistant construction. If you're a crypto holder who travels for work or just moves around a lot, you already know the struggle: Safnect crypto wallet that actually fits your life.
Program or simulation errors
Read the failing instruction and its program log. Common causes include invalid accounts, incorrect instruction data, slippage limits, authority or signer problems, and application-specific preconditions. Fix the input or program condition first. A higher fee cannot repair a deterministic program error.
Should you pay a priority fee?
Solana fees have a base component and an optional prioritization component. A priority fee can improve scheduling priority when the network or a particular block producer is busy, but it is variable and never a guarantee that a transaction will land.
Use this order of operations:
- Confirm that the transaction is valid and that the fee payer and token accounts are funded.
- Identify whether the problem is actually congestion or endpoint delay rather than a program error or expired blockhash.
- Check current fee guidance from the application or a reliable fee-estimation source.
- Set a priority fee appropriate to the transaction’s compute-unit limit and current conditions, then sign a new transaction.
Do not increase the fee to solve an insufficient-balance error, missing account, invalid instruction, or expired blockhash. Fees are charged even when execution fails, so repeated fee increases can add cost without improving the outcome. Solana documents a maximum of 1.4 million compute units per transaction; compute settings and fee choices should match the actual instructions rather than using an arbitrary maximum.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When the RPC endpoint is the real problem
RPC infrastructure sits between your wallet or application and the cluster. A shared public endpoint can be rate-limited, overloaded, or behind the current slot. It may return a fast response containing stale account data, or accept a transaction while confirmation polling times out.
Symptoms of endpoint trouble
- The same signature is visible from one endpoint but not another.
- Account balances or recent blockhashes lag noticeably behind the network.
- Requests return intermittent timeouts, HTTP errors, rate-limit responses, or inconsistent commitment results.
- Submission succeeds, but status polling repeatedly returns null from the same node.
For a personal wallet, switching to the wallet’s alternate endpoint or waiting for service recovery may be enough. Keep the original signature and recheck before resubmitting. For a production application, Solana advises against relying on shared public endpoints for payment flows.
Rank #4
- All your digital assets in one place. You can manage thousands of crypto including Bitcoin, Ethereum, Solana, Tether and more.
- Connectivity: USB-C cable connection only. No Bluetooth.Compatible with the Ledger Wallet crypto app, both desktop (Windows, macOS, Linux) and mobile (Android only). Not compatible with iOS.
- Protect your digital assets with the industry's best security: keep your private keys offline in your private signer, battle-tested by the Donjon's white hat hackers, CC EAL 6+ certified Secure Element, constantly updated Ledger OS.
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Choose the colors that match your style: express your personality and your crypto management mood, color code your signers, one for each use (trading, staking, HOLDing...).
Production endpoint checklist
Measure providers from the region where your application runs. Compare:
- Median and tail latency during normal and peak load.
- Error, timeout, and rate-limit rates.
- Returned-slot freshness and consistency across commitment levels.
- Request, bandwidth, WebSocket, and concurrency limits.
- Transaction routing, retry, and status capabilities.
- Portability, fallback options, and operational support.
Use request timeouts, bounded retries with exponential backoff, and health checks. Avoid unbounded retry loops, which can multiply submissions and fees. When possible, perform blockhash retrieval, simulation, sending, and confirmation against a healthy, consistent endpoint; mixing a current node with a lagging node can make a valid transaction appear invalid or missing.
A safe recovery sequence for individual wallets
- Copy the signature. Save it with the intended recipient, amount, and time.
- Check status. Query
getSignatureStatusesand inspect the transaction in an explorer if useful. - Read the error. Distinguish pending, endpoint visibility, blockhash expiry, balance errors, and program failures.
- Check duplication risk. Never create a replacement payment until you have established that the original did not execute.
- Correct the cause. Fund SOL, fix token accounts or instruction data, or obtain a fresh blockhash as appropriate.
- Rebuild and sign. A new blockhash or corrected instruction requires a newly signed transaction.
- Submit once and monitor. Record the new signature and poll it at the commitment level your use case requires.
Limits and costs worth knowing
| Item | Documented value | How it affects troubleshooting |
|---|---|---|
| Maximum standard transaction size | 1,232 bytes | Oversized transactions must be redesigned; resubmitting the same bytes will not reduce their size. |
| Recent-blockhash processing age | 150 slots maximum | After the validity window closes, fetch a fresh blockhash and rebuild. |
| Base fee | 5,000 lamports per signature | Charged in SOL; total cost can vary with signatures and optional prioritization. |
| Maximum compute units | 1.4 million per transaction | Compute demand and prioritization settings should reflect the transaction’s actual instructions. |
These are protocol and documentation parameters, not average confirmation times or guarantees. No reliable network-wide failure rate or universal landing time should be assumed.
Preventing repeat failures
- Display the signature immediately after submission and keep it in application logs.
- Separate “submitted,” “processed,” “confirmed,” and “finalized” states in the user interface.
- Poll status with bounded backoff and show the last checked time and endpoint.
- Keep enough SOL for base fees and expected prioritization, separate from token balances.
- Refresh the blockhash close to signing and sending, especially during congestion.
- Simulate and validate account, authority, amount, and slippage inputs before sending.
- Monitor endpoint latency, slot freshness, error rates, and rate limits.
- Design an explicit fallback plan, but require signature-status checks before any retry that could duplicate a state change.
The Bottom Line
The safe rule is simple: preserve the signature, verify status, diagnose the error, and only then retry or change fees. Waiting is appropriate for a still-valid transaction; rebuilding is required for an expired blockhash; funding or instruction fixes are required for balance and program errors; and recurring visibility or timeout problems call for a healthier RPC setup.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
