Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesDo not send the payment again just because your app says “pending.” First find the transaction in the app and check its transaction ID or hash on an explorer for the exact network used. That shows whether the transfer was broadcast, is still awaiting confirmation, failed, or has confirmed on-chain. If it has confirmed but the recipient has not credited it, the next step is usually with the receiving service—not another payment.
What “pending” means
“Pending” is a status, not a definitive answer about whether a payment failed or whether the recipient has received usable funds. Blockchain.com Support Center distinguishes three stages: a transaction is pending when submitted to the network but not yet included in a block; confirming when included in a block but short of the service’s required confirmation count; and confirmed when it has reached that service’s threshold. As Blockchain.com notes, “This number varies by blockchain.” A service may also wait for more confirmations than another service does.
An app’s label can describe different processes. A normal on-chain transfer, an exchange deposit or withdrawal, an in-app transfer, a purchase, a swap, and a Lightning payment do not necessarily share the same status path. For example, Coinbase describes Lightning invoice status separately from ordinary on-chain transfers, and some email or phone transfers may remain unaccepted and be cancellable under Coinbase’s rules. Check the transaction type before choosing a remedy.
Check the transaction before taking action
- Open the transaction details. Find the transaction ID or hash and the stated network in the app. If someone else sent the funds, ask them for the ID or explorer link. An internal platform transfer may not have an on-chain ID; ask that platform for its transaction reference.
- Search the ID on an explorer for that exact network. A transaction searched on the wrong network’s explorer can appear not to exist. Check whether the explorer reports it as not found, pending, failed, or confirmed, and review the destination and confirmation count. An explorer shows public blockchain data; it cannot change a transaction or access your wallet.
- Compare the payment details. Match the receiving address, asset or token, network, and amount against the instructions from the receiving service. Check whether a memo or destination tag was required and included. If the address or network is wrong, recovery may be difficult or impossible and is not guaranteed.
- Check the receiving account separately. Confirm the service supports that asset and network for your account and region, and look for notifications about identity verification or other requested account information. On-chain confirmation does not necessarily mean the recipient’s app has credited the funds.
Choose the next step based on what you find
| Explorer or app finding | What it may mean | What to do |
|---|---|---|
| Explorer cannot find the transaction | The sender may not have signed or broadcast it, or the ID or network may be wrong. | Verify the ID and network. Ask the sender or originating platform to confirm the transaction was broadcast and investigate before attempting another payment. |
| Explorer shows pending or unconfirmed | The transaction has not reached the relevant confirmation threshold. A low fee, network congestion, slow block timing, or an unconfirmed transaction it depends on can contribute. | Check the sender’s wallet and the network conditions. If the sender set a low fee, only that sender may be able to raise it, and only if the wallet and network support a fee-bump option. Otherwise, waiting may be the only practical step. |
| Explorer shows failed | The transaction did not complete as shown by the relevant network or service. | Review the app’s failure details and contact the sender or originating platform if the balance or status is unclear. Do not assume a second payment is appropriate until the first transaction’s outcome is understood. |
| Explorer shows confirmed, but the balance is missing | The receiving service may require more confirmations, may not support the asset or network for that account, or may need to complete account checks or internal crediting. | Review the receiving account’s deposit rules and notifications, then contact the recipient service through its official support route with the transaction ID. |
| App shows no incoming payment, but the sender has an explorer link | The app may not have refreshed, or the receiving service may not yet have credited the transfer. | Reopen or refresh the app, update it if needed, and check the explorer status and destination before escalating to the receiving service. |
Why a transaction or deposit can be delayed
- Network congestion or fee settings: Transactions with fees that are low relative to current demand may wait longer for inclusion. A fee-bump option, if available, is controlled by the sender’s wallet; it is not a universal feature.
- Confirmation requirements: A transfer can be in a block but still below the receiving service’s threshold. The threshold is service- and network-specific.
- App or platform processing: A wallet screen may be stale, a platform’s node may be syncing, or the receiving service may apply its own crediting process or account checks after the blockchain transfer is confirmed.
- Transaction-specific conditions: A transaction may depend on an earlier unconfirmed transaction, conflict with a double-spend attempt, or be a Lightning payment or custodial purchase with a different status mechanism from a standard on-chain send.
- Incorrect details or unsupported route: A wrong network, address, missing required memo/tag, or unsupported asset can prevent funds from appearing as expected. Whether a transfer can be recovered depends on the service and circumstances; recovery is not assured.
How long should you wait?
There is no reliable universal deadline. Check the live explorer status and the receiving service’s confirmation requirement; congestion, fee settings, asset, and platform processing all affect timing.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
Provider guidance can help set expectations, but it is not a guarantee for every wallet or network. Exodus’s Knowledge Base, updated September 21, 2026, says most transactions are confirmed within 5–60 minutes, and lists typical pending estimates of 60 minutes or less for Bitcoin and five minutes or less for Ethereum, BNB, Cardano, Litecoin, and Solana. Those are Exodus estimates, not universal limits.
Coinbase’s support guidance is likewise specific to Coinbase: one send-troubleshooting page advises waiting at least 30 minutes before checking the explorer for a pending send, and Coinbase describes some network-sync delays as usually under an hour. Its guidance also says some received transfers may be credited within 3–5 business days after requested account actions are completed. These figures do not establish a deadline for another app or a guarantee that a particular transfer will complete.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
BitBox’s Bitcoin-specific guidance describes six confirmations as the threshold used in BitBoxApp’s Bitcoin status display. That is not a universal threshold for Bitcoin services or for other blockchains.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When to contact support—and what to share
If the explorer confirms the transfer but the receiving balance is still missing, contact the receiving wallet, exchange, merchant, or payment provider. If the explorer cannot find the transaction or it remains unbroadcast, contact the sender or originating platform. Use the official app or website support route rather than a search-result phone number or unsolicited message.
Provide the public transaction ID or hash, the network, the asset, the amount, the destination address as appropriate, and a concise description of what the explorer and app show. Never share a recovery phrase, private key, password, or one-time sign-in code with support or anyone claiming they can reverse the payment. A block explorer can display public transaction data, but it cannot access your wallet or alter the transaction.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Rank #4
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.
