My crypto from Coinbase/Binance hasn't arrived in my wallet. What should I do?

Troubleshooting Missing Crypto Transfers

1. Verify the transaction hash on a blockchain explorer such as Etherscan for Ethereum-based tokens or Blockchain.com for Bitcoin. Paste the TXID provided by Coinbase or Binance into the search bar. If the transaction appears unconfirmed, it may be stuck due to low network fees.

2. Confirm that the receiving wallet address matches the intended network. Sending USDT on the Tron network to an Ethereum-compatible address will result in permanent loss unless the destination wallet supports both networks.

3. Check whether your wallet supports the specific token standard. For example, attempting to receive BEP-20 tokens in a wallet that only accepts ERC-20 will prevent visibility—even if the funds are technically on-chain.

4. Review the withdrawal confirmation status inside the exchange interface. Some platforms display “Processing” or “Pending” for extended periods during maintenance or high-volume settlement windows.

Exchange-Specific Withdrawal Delays

1. Binance enforces mandatory 24-hour withdrawal holds for accounts flagged under KYC review or after recent security changes like new device logins.

2. Coinbase applies dynamic processing windows depending on asset type—stablecoin withdrawals often settle within minutes while privacy coins like Monero may require manual validation and take several hours.

3. Both platforms throttle outbound transfers during periods of elevated on-chain congestion. This is especially common during NFT minting surges or major market volatility events.

4. Withdrawals initiated during scheduled platform maintenance—often announced via official Twitter or status pages—may queue silently without user-facing notifications.

Wallet Configuration Errors

1. Importing a mnemonic phrase into a wallet that uses a different derivation path (e.g., BIP-44 vs. BIP-49) can cause balances to appear zero despite correct seed recovery.

2. Some wallets require manual token addition. Even if ETH arrives, ERC-20 tokens like UNI or LINK won’t auto-display unless their contract addresses are explicitly added to the token list.

3. Hardware wallets like Ledger or Trezor must have the correct app open and screen unlocked during transaction signing. Failure to do so results in silent rejection with no on-chain trace.

4. Browser extension wallets such as MetaMask may fail to detect incoming transfers if the network RPC endpoint is misconfigured or temporarily offline.

On-Chain Confirmation Thresholds

1. Bitcoin transactions typically require six confirmations before exchanges credit internal accounts; fewer than that may delay wallet visibility even after first confirmation.

2. Ethereum mainnet deposits usually need twelve confirmations, though Layer 2 solutions like Arbitrum or Optimism reduce this to just one or two—provided the receiving wallet recognizes the L2 environment.

3. Solana requires thirty-one confirmations for finality, and many custodial wallets do not reflect balances until that threshold is met.

4. Polygon transfers may show instantly in block explorers but remain invisible in non-Polygon-aware wallets unless the MATIC network is manually enabled.

Frequently Asked Questions

Q: Can I reverse a crypto withdrawal once it’s broadcast? No. Blockchain transactions are immutable. Once confirmed, reversal is impossible without cooperation from the recipient.

Q: Why does my exchange show “Completed” but my wallet shows zero balance? The exchange marks status based on its internal ledger update—not on-chain arrival. Discrepancies arise when network fees were insufficient or the destination address was incompatible.

Q: Does using a privacy-focused wallet like Samourai affect receipt visibility? Yes. Such wallets use advanced UTXO management and may not recognize standard deposit patterns. Funds sent directly to base addresses might require manual coin control import or Stowaway setup.

Q: What if the transaction hash returns “Not found” on all explorers? That indicates the transaction never left the exchange. Contact support immediately with your withdrawal ID and timestamp—do not assume automatic retries.