Free tools Windows power users keep installed
One-click scans. No signup required.
If a crypto remittance is delayed, first find out whether the sending service has broadcast it, whether it is still awaiting blockchain confirmations, or whether it succeeded on-chain but has not been credited by the receiving platform. Locate the transaction ID (TxID) in the sender’s history, then check it on an explorer for the exact network. That tells you which service to contact and what evidence to provide.
Start by locating the transaction ID
Open the sending service’s withdrawal or transfer history and find the transaction status. Look for a TxID, transaction hash, or explorer link. A request marked “pending” without a TxID may still be at the sending service and not yet on the blockchain; a withdrawal request, network confirmation, and destination deposit are separate stages, as Binance explains.
If you have a TxID, open it in a block explorer for the network actually used. Check the result (pending, successful, or failed), confirmation count, time, sending and receiving addresses, asset, amount, and fee. OKX’s explorer guidance describes these details. An address that looks familiar or uses a similar format does not establish that the correct network was selected.
Choose the next step based on what the record shows
No TxID: ask the sender or sending service
Check the withdrawal history and any account or email notices to see whether the request is still processing, needs approval, or failed before broadcast. If it remains in processing beyond the sending provider’s stated guidance, contact that provider through its official support channel. Timing advice is provider-specific: a Binance FAQ dated January 3, 2018 says a TxID is typically generated within 30–60 minutes and recommends contacting support if one is still absent six hours after email confirmation. The page warns its information may be outdated, so verify the current instructions in your account rather than treating those intervals as general crypto deadlines.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
Pending or unconfirmed: monitor confirmations and check with the sender if they stall
Look up the receiving service’s required confirmation threshold for that asset and network, then monitor the explorer. Confirmation speed varies with network conditions and provider requirements; congestion, low fees, or a temporary node or service issue can contribute to a delay. Circle’s USDC Bridge guidance advises monitoring confirmations and waiting while they increase; Coinbase and OKX also explain pending transactions and confirmation delays.
If the count is not progressing, ask the sender or sending service to investigate the transaction. Do not send another transfer simply to test whether the first one worked. Some self-custody wallets may offer replace, accelerate, or rebroadcast options, but availability depends on the chain, wallet, and transaction state. Follow the wallet’s official instructions before attempting one.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Successful on-chain, but not credited: contact the receiving platform
Compare the transaction with the receiving platform’s deposit instructions. Check that it supports the exact asset and network, that the amount meets any deposit minimum, that the required confirmation threshold has been reached, and that any memo or tag was included. Verify the complete destination address and memo/tag against the transaction record.
Also inspect the receiver’s account and wallet history, asset filters, status notices, alerts, and any requests for identity or profile information. A successful blockchain transaction does not by itself mean an exchange has credited the deposit: Coinbase says required account actions can delay crediting, while Binance directs users to the receiving platform after blockchain confirmation.
Once the transaction is confirmed, the route details match, and the platform’s stated confirmation threshold is met, contact the receiving platform through its official support channel. Give it the TxID and transaction details, and ask whether the asset and network are supported and whether manual credit or a recovery process is available. Recovery depends on the provider’s policy, the asset, network, and region; neither credit nor recovery is guaranteed. See also Coinbase’s guidance and OKX’s explorer guidance.
Wrong address, network, asset, or memo/tag: stop and ask the destination service
Record exactly what was sent, the network used, and the destination details. Contact the service that controls the destination address using its official help center and ask whether recovery is possible. A missing or incorrect memo/tag can leave a platform unable to identify a deposit. Funds sent to the wrong address or over an unsupported network may be unrecoverable: Coinbase says it cannot recover funds sent on the wrong network, and OKX warns that recovery is not guaranteed.
Rank #4
Ignore unsolicited offers to unlock, reverse, or recover funds for a fee. Reach the exchange or wallet’s official support site independently; do not rely on a stranger’s link or contact details.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to include in a support request
Prepare the details that let support identify and trace the transfer:
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
- TxID or explorer link, if one exists.
- Asset and amount, plus the sending and receiving networks.
- Complete destination address and any memo or tag.
- Date and time, including timezone.
- Current transaction result and confirmation count.
- Name of the sending and receiving service.
- Relevant withdrawal or deposit history and screenshots.
For a USDC Bridge issue, Circle requests the transaction hash, wallet address, provider and version, source and destination networks, date and time, USDC amount, and details of the web or mobile app and browser or operating system. In its no-TxID escalation example, Binance asks for a withdrawal-history screenshot.
Provider timing is not a universal deadline
Published support-page estimates apply to specific providers and transfer types, not every crypto remittance:
- Coinbase says most transactions complete within 30 minutes. This is Coinbase guidance, not a guaranteed arrival time for other services or networks.
- Coinbase says credit may take 3–5 business days after requested account actions are completed. This refers to the circumstances described on that Coinbase help page, not a general deposit-processing window.
- Coinbase says a Lightning invoice can remain pending for up to 72 hours or until the sender completes it. This is specific to Lightning, not ordinary on-chain transfers.
Check the current status and guidance in the relevant provider’s account or help center; support policies, confirmation counts, supported networks, and recovery processes can vary by provider and jurisdiction.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
