Why Did Your Token Transfer Succeed but the Recipient Says They Never Got It?
When a token transfer shows as successful on a block explorer but the recipient claims they never received it, the most common reasons are that you sent the token to the wrong address, the recipient is checking the wrong contract address, the transfer went to a contract instead of a wallet, or the token was intercepted by a malicious contract. Here is how to diagnose each scenario step by step.
Check the recipient address first
The simplest explanation is a typo or copy-paste error in the destination address. A single wrong character will send the token somewhere unintended. On the block explorer, locate the transaction and inspect the "To" field under the transfer details. Compare it character by character with the address the recipient gave you. If they do not match, the token went to the wrong address, and recovery depends on whether that address is controlled by someone you can contact.
Verify the token contract address
If the "To" address matches, the next likely problem is that the recipient is looking at the wrong token on their end. Every token has a unique contract address. The recipient may be checking their wallet or explorer for a different version of the same token - for example, a bridged version versus the native one. On the transaction page, note the "Contract Address" or "Token" field. Ask the recipient to check their wallet or an explorer for that exact contract address. If they see zero balance, the token may have been sent to a contract address, not a wallet.
Determine If the Recipient Is a Contract, Not a Wallet
Some addresses are smart contracts, not individual wallets. If you sent a token to a contract address that does not have a function to accept or hold tokens, the transfer will appear successful on the explorer (the transaction executes and emits a Transfer event), but the tokens become trapped in the contract. The explorer will show the transaction as complete, but the recipient address will show a token balance increase only if the contract implements a standard like ERC-20's transfer or transferFrom. To check, look up the recipient address on the explorer. If its page says "Contract" instead of "Wallet" or shows code, it is a contract. If the contract lacks a withdrawal function, the tokens are not retrievable.
Look for Internal Transactions or Approvals
If the recipient is a contract, the token may have been immediately forwarded or converted via an internal transaction. On the transaction detail page, check the "Internal Transactions" tab (sometimes called "Internal Txns" or "More"). If the token was sent to a contract that automatically swaps or wraps it, the internal transaction list will show the resulting action. The recipient might see a different token in its place, or the token could have been sent to a third address.
Check for a Malicious Contract That Drains Tokens
Some contracts are designed to intercept token transfers. If you send a token to a contract that has a transfer or fallback function that re-routes or burns the tokens, the explorer will still show the initial transfer as successful, but the final destination may be a different address - often one controlled by the contract deployer. Use the explorer's "Token Transfers" or "ERC-20 Transfers" section for the transaction to see the full list of token movements. If the token moves from your address to the contract, then immediately from the contract to another address, the recipient never actually held it.
Confirm the recipient's wallet settings
Sometimes the recipient's wallet interface hides tokens. In MetaMask, for example, a token will not appear unless the user adds it manually by contract address. Ask the recipient to add the token contract address to their wallet. If the explorer shows the recipient address has a positive token balance, the wallet is simply not displaying it. The "Token Holders" list for that token contract will show the recipient's balance if it exists.
Check for a Transfer Fee or Burn
Some tokens include a fee on transfers that sends a portion to a burn address or a fee collector. The transaction may show a reduced amount arriving at the recipient. On the transaction's "Token Transfers" tab, look for multiple transfer events. If one of them goes to address 0x000...000 (a burn address) or a fee wallet, the recipient only gets the remaining amount. They may believe they received nothing if the amount is zero or negligible.
When the Block Explorer Shows Success but Balance Is Zero
If you have verified the address, contract, and internal transactions, and the recipient's balance on the explorer for that token contract is zero, the transfer likely did not happen as you think. Re-check the transaction hash on a different block explorer for the same chain. Some explorers cache data incorrectly. If the transaction is not found on another explorer, your original explorer may have shown a pending transaction that later failed without updating. In that case, the token never left your wallet. Check your own balance for that token contract on the explorer to confirm.
If all else fails
Gather the transaction hash, the sending and receiving addresses, and the token contract address. Post on a blockchain-specific forum or Discord for help. Include the explorer links. Do not share private keys or seed phrases with anyone offering help.
Not financial advice. sonnyonsol.xyz publishes market data and general information about staring robot. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.