Crypto transfer pending or missing? What to check

A crypto transfer pending in an app is not necessarily lost. Before sending again, find the transaction hash (TxID), open the explorer for the network actually used, and check whether the transaction was broadcast, is still awaiting confirmation, failed, or succeeded. The right next step depends on that result. A receiving platform may still say “pending” after on-chain confirmation because crediting your account is a separate process.

If you only have a screenshot or an order receipt, ask the sender for the hash and network name. Do not send more crypto as a test until you understand the first transfer. Anyone who asks for your recovery phrase, private key, or login code to “locate” the funds is not doing ordinary transaction tracing.

Crypto deposit not received? Start with this checklist

1. Find the hash in the sender's history. It identifies the on-chain transaction. An internal withdrawal request number is not the same thing.
2. Confirm the asset and network selected by the sender. USDT on Ethereum, Polygon, and Tron follows different deposit routes. The ticker alone does not make the networks interchangeable.
3. Open an explorer for the network used, not the network you expected. Paste the hash and inspect status, recipient, and token transfer details.
4. If the transaction succeeded, compare the actual recipient with the address the receiving service supplied. For an EVM token, check the token transfers tab. The main transaction's To field may be the token contract rather than the person receiving the tokens.
5. Separate on-chain status from platform credit. If the correct transfer is confirmed but your balance is missing, contact the receiver's official support. If it is not confirmed, the sender must investigate with the sending wallet or platform.

There is no universal waiting period. Networks and services set different confirmation and crediting rules. Coinbase's troubleshooting guide separates transaction status, explorer evidence, and account credit; another service may use a different threshold.

Which block explorer should you use?

A block explorer is a public way to inspect a network's records. Ethereum's documentation lists the useful fields: hash, status, block, sender, recipient, and token transfers. Match the explorer to the network the sender chose:

This is not a list of every network. For another chain, use an explorer linked by the sending wallet or the network's official documentation, and check the domain carefully. A fake explorer may try to make you connect your wallet. Looking up a public hash never requires a recovery phrase or a signed transaction.

On Ethereum and Polygon, a USDT transfer may show the token contract as the transaction's To address. To find the actual token recipient, inspect the token transfer event, recipient, contract, and amount. Reading only the first To field can produce the wrong diagnosis. If the hash belongs to a bridge, there is also a destination leg: success on the source chain alone does not prove delivery on the destination chain.

What do “not found,” “pending,” “failed,” and “success” mean?

“Not found” is easy to misread. Someone may paste a Polygon hash into Etherscan. A platform might show a withdrawal request as “approved” before broadcasting an on-chain transaction. Ask the sender what was actually submitted. A failed search does not establish that funds disappeared.

For Bitcoin, the first confirmation arrives when the transaction enters a block. Bitcoin.org explains that block timing is probabilistic; a fee below current demand can make the wait longer. Solana uses the distinct “processed,” “confirmed,” and “finalized” commitment levels described in its official documentation. There is no single confirmation count or fixed delay that applies to every asset, network, and service. Check the receiving service's rule for your exact asset and network.

Can you speed up or cancel a pending transfer?

That depends on who controls the sending wallet and what its software supports. If you sent Bitcoin from a wallet that offers replace-by-fee (RBF), you may be able to replace a pending transaction with another one carrying a higher fee. Trezor documents that action for its wallet. It is not a universal button for every Bitcoin wallet or exchange withdrawal. The recipient cannot change the fee attached to someone else's transfer.

For an exchange withdrawal, look at the exchange's own history and official support channel. Do not request a second withdrawal merely because the first is slow: it may still confirm. Other networks have different replacement, expiry, or failure mechanisms. Without the exact status, “cancel” is a dangerous shorthand. An attempted cancellation is not evidence of a completed refund.

There is no fee that guarantees priority. Costs change with the network and demand. The Portuguese guide to crypto withdrawal costs explains the components. Never sign an “unlock” transaction proposed by an unknown contact.

The chain shows success, but the balance is missing

First, verify the exact asset and recipient. Compare the full address, the network, and the token contract. A similar-looking address or matching ticker is not enough. If the network differs from what the receiving service accepts, see the Portuguese guide to sending crypto on the wrong network. Sometimes only the operator of the receiving address can assess recovery; other cases cannot be recovered. Do not assume either outcome without establishing who controls the destination.

If the network, asset, and address match, check the receiver's crediting policy. It may need more confirmations, be processing the deposit, or need to investigate an internal issue. Open a case through its official support channel and provide the hash, network, asset, token contract when relevant, amount, time, and recipient address. A hash is public; your password, passkey, and recovery phrase are not. Never provide those credentials to support.

For a deposit into Picnic, the app displays an address after you choose the asset and network, and it detects an incoming transfer. You still need to verify that the selected asset-network combination is supported on that deposit screen. If a confirmed transfer to the supplied address has not appeared, share the hash with official in-app support for investigation rather than repeating the deposit. For a withdrawal sent through Picnic, find the hash in the transaction history when available and verify the outgoing network before contacting the destination. The Portuguese guide to choosing a USDT network may help prevent the next mismatch; it cannot change a transfer already sent.

Before you make another transfer

Keep the evidence for the first attempt: hash, network, status, address, and token. If it is still pending, the sender is your starting point. If it succeeded on the correct network but was not credited, contact the receiving platform. If the network or destination differs, pause new attempts and investigate the actual recovery options, without assuming a guarantee.

For any new transfer, check the receiving deposit screen for supported assets and networks, compare the entire address, and consider a small test that meets the service's minimum deposit and makes sense after fees. On-chain confirmation proves one stage of the transfer, not necessarily the whole journey. That distinction prevents both panic and accidental duplicate sends.

---

Picnic is a technology platform that lets users independently interact with USDC, a U.S. dollar-pegged stablecoin issued by Circle, on public blockchains. USDC is not legal tender in Brazil.

Displayed exchange rates vary with market conditions. The final applicable amount is the one shown on the transaction confirmation screen. Cryptoassets involve risks, including volatility and loss of peg.

Picnic does not custody user assets and is neither a financial institution nor a virtual asset service provider. Sending and receiving U.S. dollar payments through a U.S. account is offered in partnership with Noah Savings Inc. Terms and conditions apply.

Information verified in April 2026.