A pending crypto transfer can mean several different things: your wallet is still preparing a request, the network has seen it but has not included it, or an exchange is waiting before crediting your account. The right response depends on which stage has stopped. Pressing send again before identifying that stage can create a second payment.
Start with the transaction record, then choose an action that matches the evidence. Our crypto send overview explains the normal transfer flow; this guide focuses on finding where a particular transfer stands and deciding whether to wait, correct a problem, or contact the service involved.
Collect the details before changing anything
Open the original activity entry in the sending wallet or exchange. Record the asset, exact network, amount, destination, submission time, and transaction identifier. Depending on the network, that identifier may be called a hash, transaction ID, or signature. An exchange withdrawal reference can be an internal ticket number rather than a blockchain identifier.
Use the explorer for the network actually selected when sending. The same address can appear on several networks, so searching an Ethereum transfer on a different chain will not establish whether it exists. If the explorer says it cannot find the identifier, check the copied text and network before drawing a conclusion.
Compare the destination against the recipient's original instructions, including any memo or tag. The wallet address and network checks are useful here. Save a screenshot of an error message, but keep your recovery phrase, private keys, passwords, and account security codes out of any troubleshooting record.
Read the status as a stage in the process
Not yet broadcast: the request has not reached the network
A signing prompt, withdrawal review, or preparing message is not proof of network submission. A hardware wallet may still need approval. A custodial service may be processing its own withdrawal queue. A connection problem may prevent the wallet from submitting a signed transaction.
Check whether you completed the signing step and whether the sending service reports a submitted transaction identifier. If an exchange has not supplied one, inspect its withdrawal status and contact its support when necessary. Do not try to solve an internal withdrawal review by sending more assets. An explorer cannot show an instruction that has never reached the network.
Pending: known to the network, awaiting inclusion
A pending record generally means the transaction has been observed but is waiting to enter a block. A transaction hash identifies the request; it does not prove the recipient has been paid. Demand for block space, the offered fee, or a dependency on an earlier transaction can affect progress.
On Ethereum, transactions from the same account use sequential nonces. An earlier unresolved nonce can hold up later requests from that account. Find the earliest unresolved transaction rather than repeatedly raising the fee on the newest one. Our Ethereum gas and ERC-20 transfer guide explains the account and fee details that matter when investigating that queue.
Failed or reverted: included, but the intended action did not complete
Check whether there is a block record and execution result before treating a wallet's failed badge as an on-chain failure; some labels also cover local submission errors.
A failed on-chain transaction differs from a request that never reached a block. On Ethereum, a reverted transaction does not preserve its intended state changes, but gas used for execution is still charged. A lower wallet balance can therefore reflect a fee even though the transfer itself failed.
Read the execution result and any decoded error. Insufficient gas, an unmet contract condition, or another application error needs diagnosis before another attempt. Increasing a fee does not fix every failure. Repeating the same invalid instruction can produce another failure and another execution charge. Also check whether a successful earlier approval was a separate transaction from the transfer you intended.
Dropped or replaced: locate the transaction that now matters
A dropped label usually describes a transaction an observer no longer keeps in its pending pool. It is not a universal cancellation receipt. Different services can have different views of pending transactions, and a locally missing record alone does not prove the signed request can never be included.
A replaced Ethereum transaction has been superseded by another transaction using the same sender and nonce. Follow the replacement identifier and read its destination, amount, and status. A replacement might be the same payment with a higher fee, or a cancellation attempt. The old hash's label cannot tell you which outcome occurred. Keep both identifiers together until you have established the replacement's result.
Choose a response supported by your wallet
If a valid transaction is simply awaiting inclusion, waiting may be reasonable when timing is flexible. Compare its fee with a fresh estimate from your wallet, but treat predicted completion times as estimates. A busier network can change the conditions after submission.
Some Ethereum wallets offer speed-up and cancellation controls. Speeding up typically submits a replacement using the same nonce with a higher fee. Cancellation is also a competing transaction, so it is an attempt, not an undo button. MetaMask's official pending-transaction guide describes these options and their limitations. Use the instructions for your actual wallet and network; confirm the revised cost before signing.
A transaction that has already confirmed cannot be canceled through a pending-transaction control. If a cancellation was submitted, continue watching both records: the original may have confirmed before the cancellation was accepted. A wallet notification that says cancellation requested is not evidence that the cancellation succeeded.
Do not apply one network's retry method everywhere
Ethereum nonce instructions are not a universal procedure. Bitcoin wallets can offer their own fee-bumping features, with availability depending on the transaction and wallet. Typical Solana transactions use a recent blockhash and can expire before landing; their lifetime needs to be checked through the wallet's network-specific process.
For any network, establish whether the original request remains capable of confirming before creating a new payment. If the wallet and explorer disagree, preserve the identifiers and seek the wallet's documented troubleshooting guidance. Clearing a display or reinstalling an app is not a blockchain cancellation.
Confirmed on-chain, but the recipient cannot use it
First confirm that the payment succeeded on the intended network and that the correct asset reached the expected address. Token transfers may require inspecting the token movement details rather than looking only at the transaction's native-coin value. Then distinguish a wallet display problem from a service crediting problem.
A self-custody wallet may be showing a different account or network, or may need the correct token added to its asset display. An exchange can require more confirmations than the explorer's first confirmation and apply its own deposit checks. The blockchain's successful status does not establish that the exchange has credited your particular customer account.
Review the exchange's supported asset and network, deposit requirements, and any required memo or tag. Check its deposit history and service notices. If these details do not match, additional waiting may not fix the issue. Our guide to sending crypto to an exchange covers those destination requirements. Do not repeat a confirmed payment to make the first deposit appear.
Build a support request that can be investigated
Give the relevant provider the transaction identifier, network, asset, amount, destination, timestamp with timezone, and the exact difference between its display and the explorer. For a replacement, include both hashes. For an exchange deposit, include the deposit reference and memo or tag that was used.
State one precise question: has this withdrawal been broadcast, why did this execution fail, or why has this confirmed deposit not been credited? Contact support through the provider's verified app or website. A public transaction identifier is sufficient for many checks; nobody needs your recovery phrase to inspect it.
Conclusion: resolve the existing transfer before retrying
Troubleshooting starts by identifying the stage that needs attention. An unsubmitted request, pending transaction, failed execution, replacement, and uncredited deposit each call for a different response. Keep the evidence, verify the network, and follow the status of the transaction that can actually settle. Create a new payment only after you understand the original outcome and have corrected the reason it did not achieve the intended result.
