Recommended Free Tools
A Solana wallet showing “sent” does not prove that the network processed your transaction. The sendTransaction method can accept and relay a signed transaction while returning its signature before the cluster confirms it. To find out what really happened, keep the signature, verify the target cluster, query its status, and check the blockhash validity window before sending anything again.
Most apparent failures fall into four groups: a preflight rejection, an on-chain instruction error, an expired recent blockhash, or an RPC endpoint problem such as lag, rate limiting, or a disconnect. The safe response depends on which group you have.
As an Amazon Associate I earn from qualifying purchases.
What “pending” and “sent” actually mean
Solana exposes several different events that wallets often compress into one status label. A successful RPC response means the node accepted the request well enough to return a transaction signature. It does not guarantee that the cluster processed or confirmed the transaction. Signature verification and simulation preflight can still produce an error, and acceptance by one RPC does not prove forwarding to a leader.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems| Observation | What it proves | What it does not prove |
|---|---|---|
RPC returned a signature from sendTransaction |
The receiving RPC performed its request-level checks and returned the transaction’s signature. | That the transaction reached a leader, executed, or will be confirmed. |
processed |
The node has seen the transaction in its latest view. | That the result cannot be rolled back. |
confirmed |
The transaction has direct votes from a supermajority of active stake. | The strongest available finality guarantee. |
finalized |
The cluster has reached its strongest confirmation state for the transaction. | That every wallet or explorer is querying the same endpoint and commitment. |
getTransaction returns a record |
Transaction details are available at the requested commitment. | That a different RPC endpoint or commitment will show the same record immediately. |
getTransaction returns null |
The requested endpoint did not return confirmed details at that commitment. | That the transaction never arrived or never executed. |
Wallets and explorers may use different RPC endpoints or commitment levels. One can still display “pending” while another already shows a confirmed result, or one can fail to find a record that is available through a different endpoint. A status query and a transaction-detail query answer different questions: the first reports what the node knows about a signature; the second returns metadata, logs, balances, and errors for a confirmed transaction.
#1 Best Overall
- 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.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
Before troubleshooting: capture the right evidence
- Transaction signature: copy the complete signature, not a shortened wallet label. This is the primary lookup key.
- Cluster: identify whether the transaction was sent to mainnet, devnet, or testnet. These are separate networks.
- RPC response: save any error text, HTTP status, commitment, and endpoint used.
- Time and wallet state: note when signing and submission occurred, plus the sender’s SOL and token balances.
- Blockhash metadata: if your application created the transaction, retain the blockhash and
lastValidBlockHeight.
Never provide a seed phrase or private key to an RPC operator, support agent, explorer, or troubleshooting form. An RPC endpoint needs the signed transaction, not your wallet’s secret. A legitimate support process can investigate a signature and public account state without asking you to export keys.
Safe troubleshooting workflow
1. Verify the signature and network
Start with the signature as your primary lookup key. Confirm that the wallet, explorer, and RPC endpoint are all pointed at the same cluster. A mainnet signature will not appear on devnet, and a correct signature queried against the wrong network can look exactly like a missing transaction. Also check that the signature was copied without omitted characters or formatting changes.
2. Query the signature status
Use the RPC method getSignatureStatuses for the signature. Record both the confirmation status and any transaction error. A status of processed, confirmed, or finalized is different evidence from a null response, and an explicit error is different again. If your client asks for a stronger commitment than the transaction has reached, it may continue to appear pending even though a weaker status is available.
A JSON-RPC request has this general shape:
{"jsonrpc":"2.0","id":1,"method":"getSignatureStatuses","params":[["<signature>"]]}Status caches are not permanent. For an older signature, request transaction history where the endpoint supports it and reconcile the result with the affected account or program state. Do not infer success from a wallet’s initial “sent” or “submitted” message. That message normally reflects RPC acceptance, not cluster confirmation.
3. Fetch confirmed transaction details
When a status indicates that the transaction has landed, call getTransaction at a suitable commitment and inspect the returned metadata, instruction logs, and error field. A null result means that the endpoint did not find confirmed details at that commitment. It does not, by itself, prove non-submission: recent status caches can miss older entries, and an endpoint may lag or prune information.
When details are available, check the transaction-level error before reading individual balance changes. A non-null error means the atomic transaction failed, even if simulation or a wallet preview showed expected instructions. Logs can identify the failing program instruction, while pre- and post-balance data can show whether the intended state change occurred.
After the blockhash window has expired, verify the outcome through transaction history or the relevant on-chain state. For a token transfer, that can mean checking the sender and recipient token accounts; for a swap or program action, check the program’s resulting state rather than relying on one missing RPC response.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Check the recent blockhash window
Every Solana transaction carries a recent blockhash. The core documentation describes a validity limit of 150 slots. Payment guidance expresses the same practical window as approximately 60 seconds, but that is not a fixed wall-clock guarantee because slot timing varies.
Rank #2
- Proven security at scale: Over 9 years and millions of cards issued with no known remote hacks, while military‑grade EAL6+ security keeps your private keys locked inside the chip. Your cryptocurrencies stay strongly protected from online attackers.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 14,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Smart backup: Use your second Tangem Wallet as your Backup keys with end‑to‑end encryption; no more papers, pictures. If one card is lost, the remaining can still restore full access, with an optional seed phrase available for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide (4.9 App Store, 4.8 Google Play) - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
When obtaining a blockhash with getLatestBlockhash, preserve both the blockhash and lastValidBlockHeight. Do not declare the transaction expired merely because a certain number of seconds has passed. Wait until the observed confirmed block height exceeds lastValidBlockHeight. Before that point, the original signed transaction may still land, so replacing it can create two valid submissions for the same payment.
A transaction can become stale while a user is approving a hardware-wallet prompt, while an application is waiting for several signatures, or while an RPC is retrying delivery. The remedy is a fresh blockhash and a newly signed transaction, but only after the original signature has been checked and the old validity window has ended.
5. Keep blockhash, simulation, sending, and confirmation consistent
Using one node to fetch a blockhash and a lagging or disconnected node to simulate, send, or confirm can create misleading errors such as blockhash not found. Use the same commitment level for blockhash retrieval and preflight. This remains important when preflight is skipped: skipping simulation does not make a stale blockhash valid.
For related operations, prefer a healthy endpoint with current slots and consistent behavior. If the wallet silently changes endpoints, compare the endpoint’s cluster, slot freshness, and response before deciding that the transaction itself is defective. A node that is behind may not recognize a blockhash that another node has just issued, while a node that is blocked may never forward a valid transaction.
6. Read the actual execution error
If the transaction reached the cluster but an instruction failed, Solana treats the transaction atomically. State changes from that transaction are reverted, while transaction fees can still be charged. Fixing the failing instruction is therefore different from fixing delivery. Do not assume that seeing a fee deduction means the intended transfer succeeded; inspect the transaction error and resulting state.
Common distinctions include:
- Insufficient SOL for fees: add enough SOL to cover the required fee and retry with a new valid transaction.
- Insufficient token balance: fund the correct token account or reduce the amount; adding SOL alone will not repair a token-balance error.
- Program or account error: inspect simulation and execution logs, account ownership, permissions, and instruction arguments.
- Invalid compute-budget instructions: correct conflicting or malformed compute-budget instructions in the transaction builder.
A retry with unchanged bytes cannot repair a wrong mint, missing account, invalid authority, or inadequate token amount. Correct the input, obtain a new blockhash when needed, sign again, and then track the replacement signature separately.
7. Treat timeouts as unknown outcomes
A client timeout only says that the client did not receive a timely response. The signed transaction may still have reached an RPC node or leader. While its blockhash remains valid, keep tracking the same signature and, where appropriate, reuse the same signed transaction rather than constructing a second payment.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →After the blockhash expires, search transaction history and verify the resulting account state. Build a replacement only after establishing that the original did not land. Repeating a withdrawal before expiry can create a double payment even when the first request appeared to time out. If an endpoint returns AlreadyProcessed, that is evidence that the same transaction bytes were seen before, not a reason to create a second logical payment.
Rank #3
- Proven security at scale: Over 9 years and millions of cards issued with no known remote hacks, while military‑grade EAL6+ security keeps your private keys locked inside the chip. Your cryptocurrencies stay strongly protected from online attackers.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 14,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Smart backup: Use your second Tangem Wallet as your Backup keys with end‑to‑end encryption; no more papers, pictures. If one card is lost, the remaining can still restore full access, with an optional seed phrase available for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
8. Check for endpoint service problems
Shared public RPC endpoints can return HTTP 429 when rate limits are exceeded or HTTP 403 when traffic is blocked. Lagging slots, dropped WebSocket subscriptions, and intermittent disconnects can also make a healthy transaction look absent. A WebSocket notification is useful, but it is not the only source of truth; after reconnecting, reconcile through HTTP status and transaction queries.
When symptoms recur, compare endpoints for:
- Current slot and block height freshness.
- Supported RPC and WebSocket methods.
- Request, payload, and concurrency limits.
- Delivery, retry, and status-tracking features.
- Fallback capacity and documented outage handling.
Reconnecting to a healthier endpoint can fix delivery or visibility. It cannot repair an invalid instruction, an inadequate balance, or a transaction that already failed on-chain. Record endpoint errors separately from transaction errors so an HTTP 429 is not misreported as a program failure.
How to interpret the most common failure causes
Expired or unrecognized blockhash
The transaction may have spent too long waiting for a signature, or it may have been sent through a node behind the one that issued the blockhash. Compare the transaction’s lastValidBlockHeight with the current confirmed block height. Rebuild with a fresh blockhash only after checking that the earlier signature did not confirm.
Free tools Windows power users keep installed
One-click scans. No signup required.
Preflight simulation rejection
sendTransaction performs signature verification and, unless configured otherwise, simulation preflight. A failed signature check or simulation can stop forwarding before the transaction reaches a leader. The returned simulation error is the starting point: correct the account, instruction, balance, or transaction-construction problem it identifies rather than repeatedly submitting the same bytes. Setting skipPreflight may change what the RPC reports, but it does not remove on-chain validation or make an invalid transaction executable.
On-chain instruction failure
An instruction can fail after the transaction is accepted and included. Because execution is atomic, earlier state changes in that transaction are rolled back, but the fee may remain charged. Use the transaction’s metadata and program logs to distinguish this from an RPC transport failure. A failed transaction and a never-landed transaction therefore require different evidence and different retry logic.
Insufficient fee balance versus insufficient token balance
These are separate failure classes. SOL pays transaction fees; a token transfer also requires enough of the specified token in the relevant token account. Supplying SOL does not increase a token balance, and supplying tokens does not pay the network fee. Check the fee payer account separately from the token source account, especially when a third-party fee payer signs the transaction.
Already processed
The transaction pipeline can reject a duplicate with an AlreadyProcessed status-cache error. This is a reason to continue tracking the existing signature, not to create a second logical payment. If the first signature’s outcome is unclear, reconcile it through status, history, and resulting account state.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchInvalid compute budget
Conflicting or invalid compute-budget instructions can be rejected during transaction validation. This points to the transaction builder or application logic, not to a failing computer or a weak internet connection. Remove or correct conflicting instructions and resubmit a newly signed transaction.
Rank #4
- 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.
Oversized or malformed transaction
The documented transaction-size limit is 1,232 bytes. Serialization or size errors indicate a construction problem, such as too many accounts or instructions, rather than ordinary network congestion. Reduce the transaction payload or split the operation only after confirming what the application requires; splitting a payment must not accidentally create two complete payments.
Why a transaction can be missing from an explorer
“Not visible” has several possible meanings:
- The signature was sent to a different cluster.
- The explorer is querying a lagging endpoint.
- The transaction is only
processedand the explorer is waiting for a stronger commitment. - The recent status cache no longer contains an old entry.
- The transaction expired before landing.
- The transaction executed but the explorer’s indexing path has not caught up.
Use the signature status and a confirmed transaction query first. For older or expired transactions, use history and the affected account or program state as the final check. Compare the explorer’s displayed cluster and commitment with the endpoint used by the wallet instead of treating a blank explorer page as proof of failure.
Retry rules that avoid duplicate payments
- Keep the original signature. Record it before any retry decision.
- Check status and commitment. Look for an explicit error, confirmation, or finalized result.
- Check blockhash validity. Compare current block height with
lastValidBlockHeight. - If still valid and outcome is unknown, track the same signed transaction. Do not create a second transfer merely because the client timed out.
- If expired, reconcile history and account state. Only then construct a replacement with a fresh blockhash.
- Change the transaction only when the cause requires it. A new endpoint may address rate limiting; it will not fix an invalid amount, account, or instruction.
For an exchange or payment processor, make the recipient-side state part of reconciliation. A withdrawal marked unknown should remain unresolved until the original signature, recipient account, or transaction history provides evidence. Automatic retries should be idempotent at the business level, not merely new submissions of the same economic action.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Guidance for applications and payment systems
Applications should persist the signature immediately, store the blockhash validity metadata, and separate submission from confirmation in their state machine. A useful sequence is “created,” “submitted,” “observed,” “confirmed,” “finalized,” “failed,” or “expired,” with the RPC error and commitment recorded alongside each transition. Store the cluster and endpoint as well, because a later query against another network cannot diagnose the original request.
Confirmation workers should tolerate WebSocket disconnects by reconnecting and reconciling through HTTP. They should also query more than one healthy endpoint when visibility is important, while avoiding contradictory commitment assumptions. A timeout should enter an “unknown” state, not an automatic “safe to pay again” state. Workers should stop polling or downgrade urgency only after the validity height has passed and history or resulting state has been checked.
Operators choosing an RPC provider should compare freshness, supported methods, request limits, delivery and retry behavior, status tracking, and fallback capacity. Do not select an endpoint solely because it is advertised as fast; representative latency and error measurements are more useful. A provider change addresses infrastructure symptoms, not an instruction that fails during simulation or execution.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Protocol values useful during diagnosis
| Value | Documented context | How to use it |
|---|---|---|
| Approximately 60 seconds | Payment guidance’s practical description of recent blockhash expiry; slot duration makes elapsed time variable. | Use as an estimate, never as a precise expiry deadline. |
| 150 slots | Core transaction documentation’s blockhash-age limit. | Track block height and lastValidBlockHeight instead of relying only on a stopwatch. |
| 1,232 bytes | Documented maximum transaction size. | Investigate oversized or malformed transactions when serialization or size errors appear. |
| 5,000 lamports per signature | Documented base fee figure in the core transaction material; fee rules can change. | Ensure the fee payer has sufficient SOL and verify current network rules before relying on the amount. |
Five thousand lamports is 0.000005 SOL, but the final amount can depend on the transaction’s signatures and current fee rules. Treat the figure as a documented base reference, not a promise that every transaction costs exactly that amount.
When to contact wallet or application support
Support can investigate a specific transaction only with useful technical evidence: the full signature, cluster, approximate submission time, RPC error or HTTP response, commitment queried, and whether the relevant account state changed. Never send secret keys. If support asks you to “retry,” first ask whether the original signature was confirmed, finalized, expired, or merely absent from their endpoint. Ask for the endpoint and commitment used if their answer conflicts with your own status query.
Best Value
- 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.
The practical diagnosis
A pending Solana transaction is not one condition. First establish whether the RPC merely accepted it, whether any node observed it, whether it reached confirmation, and whether its blockhash is still valid. Then classify the problem as preflight, execution, expiry, or endpoint service. Track the original signature through that process; only construct a replacement after expiry and an independent check show that the intended payment did not occur.
Frequently Asked Questions
Why is my Solana transaction still pending after the wallet says sent?
“Sent” usually means the RPC accepted the signed transaction and returned a signature. It does not prove cluster processing. Query getSignatureStatuses, note whether the result is processed, confirmed, or finalized, and check the same cluster and commitment used by the wallet. A lagging endpoint or an unexpired blockhash can also make a valid transaction appear pending.
How do I check whether a Solana transaction really went through?
Copy the full signature and query getSignatureStatuses. If it has landed, request getTransaction at an appropriate commitment and inspect its error and metadata. For old signatures or a null response, check transaction history and the affected account or program state. Do not rely on a wallet’s initial submission message or one explorer page alone.
Can I safely retry a timed-out Solana payment?
Not immediately. A timeout means the client did not receive a timely response; the signed transaction may still be processing. While the blockhash remains valid, track the original signature and avoid creating a second payment. After the current block height exceeds lastValidBlockHeight, check history and resulting state. Construct a replacement only after those checks show that the original did not land.
What does “blockhash not found” mean?
The receiving node does not recognize the recent blockhash, often because the transaction expired or the node is behind the node that issued it. Compare current confirmed block height with the saved lastValidBlockHeight, and keep blockhash retrieval, preflight, sending, and confirmation on a consistent, healthy endpoint. Rebuild with a fresh blockhash only after checking the earlier signature.
Why did my Solana transaction fail but still charge a fee?
Solana transactions are atomic: when an instruction fails, state changes from that transaction are reverted, but transaction fees can still be charged. Read the transaction error and program logs to identify the failing instruction. A fee deduction does not prove that a token transfer or program action succeeded.
Is insufficient SOL the same as insufficient token balance?
No. SOL pays the network fee, while a token instruction requires enough of the specified token in the correct token account. Adding SOL does not fix an insufficient-token error, and adding tokens does not pay the fee. Check the fee payer and token source accounts separately.
What should I do if an explorer cannot find my signature?
First verify the cluster and query the signature directly through a reliable RPC endpoint. The explorer may use a different endpoint, commitment, or indexing path, and old status-cache entries may no longer be available. After blockhash expiry, use transaction history and the relevant account or program state to determine whether the intended action occurred.
Can changing RPC providers fix a failed Solana instruction?
It can help with HTTP 429 or 403 responses, stale slots, disconnects, or delivery problems. It cannot fix an invalid account, amount, authority, balance, compute-budget instruction, or program argument that fails during simulation or execution. Separate endpoint-service errors from transaction-level errors before changing infrastructure.
The Bottom Line
Keep the signature, verify the cluster, query status and confirmed details, and track lastValidBlockHeight. Treat timeouts as unknown, not failed; a duplicate payment is possible while the original blockhash remains valid. Retry only after expiry and an independent history or account-state check show that the original transaction did not land.
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.
