How to recover from a crypto transaction mistake

You send a transaction.

A few seconds later, something feels wrong.

Wrong address. Wrong network. Wrong amount.

The first question is not what went wrong. The first question is whether the transaction is confirmed.

Once a transaction is confirmed, it cannot be reversed. Recovery depends entirely on where the funds were sent and who controls that destination.

This guide shows you how to react step by step, what you can still recover, and what is already lost.

👉 If you are not comfortable with how transactions work:
→ Crypto transactions: how they work

Before anything else

Stay calm.

Do not send additional funds before fully understanding what happened.

Do not trust any service offering to recover funds in exchange for payment, whether they contact you on Telegram, Discord, Twitter, or by email. They cannot reverse a blockchain transaction, and they will take your money.

Never share your seed phrase or private keys with anyone, ever.
Legitimate support will never need your seed phrase or private key to investigate a transaction.

Always verify the destination before taking any action. A second mistake can make recovery impossible.

Acting too quickly is often how a second mistake happens.

Step 1. Check the transaction status

Before anything else, check whether the transaction is confirmed.

How to do it

Open your wallet.
Go to your transaction history and click the transaction in question.
Copy the transaction hash. It is a long string of letters and numbers, starting with 0x on most networks.

Open the block explorer for the network you used:

• Ethereum → etherscan.io
• Arbitrum → arbiscan.io
• Base → basescan.org
• BNB Chain → bscscan.com
• Polygon → polygonscan.com
• Solana → solscan.io

If you are unsure which explorer to use, search for the network name followed by "block explorer".

Paste the transaction hash into the search bar and press Enter.

What the status means:

• Pending 
  The transaction has not been processed yet. You may still be able to act. Go to Step 2 immediately.
  
  If the transaction is still pending, do not treat it as a confirmed mistake yet.
  Depending on the network, the fee you paid, and current congestion, a transaction can remain pending for a long time before it confirms, is replaced, or disappears from the pending view.
  → Start with How to handle a stuck transaction.
• Confirmed or Success 
  The transaction is final. It cannot be modified or cancelled.
  → Go to Step 3.
• Failed 
  The transaction did not go through. Your funds were not sent, but you may still have paid network fees. You can stop here.

⚠️ The status can change within seconds. Check it immediately.

Step 2. Act if the transaction is still pending

A pending transaction is one of the only cases where you may still be able to intervene. Act quickly, but do not rush blindly.

Some wallets allow you to speed up, cancel, or replace a pending transaction. The exact options depend on the wallet, the network, and whether the transaction is still visible as pending.

• Speed up means resending the same transaction with a higher fee so it has a better chance of being confirmed.
• Cancel or Replace means sending another transaction with the same nonce and a higher fee. If the replacement confirms first, the original pending transaction is effectively replaced.

⚠️ If the transaction is already confirmed, these options are no longer available. Move on to Step 3.

Step 3. Identify what went wrong

Once the transaction is confirmed, recovery depends entirely on the situation. Find your case below.

At this point, you are no longer trying to cancel a transaction. You are trying to understand where the funds went.

Case 1. Wrong address

The outcome depends on whether you can identify who controls the destination address.

Check the address

Copy the destination address from your transaction. Paste it into a block explorer. Look for a label such as Binance, Coinbase, or Uniswap, whether it is a smart contract or a regular wallet, and recent transaction history.

Click on the address and review recent transactions. Repeated interactions with the same platform can help you identify it.

If the address has no label, try these tools:

• Arkham (arkm.com)
• Nansen (nansen.ai)

These tools attempt to identify known entities, but results are not always reliable and may require a paid subscription. Use them as a starting point.

Act based on what you find

The address belongs to a known service

Go to the official support page of that platform.

Open a ticket and provide:

• Transaction hash (TXID)
• Token and amount sent
• Network used

Recovery is sometimes possible, but it is slow, often involves fees, and is never guaranteed.

Support can sometimes help when the destination is a service that controls the receiving address. In that case, recovery depends entirely on the platform's internal process, policies, and willingness to intervene.

The address belongs to someone you know

Contact them directly and request a return.

Recovery depends entirely on their cooperation.

The address is unknown

In practice, the funds are lost. There is no authority to contact and no mechanism to reverse a confirmed transaction.

Case 2. Wrong network

This mistake is more recoverable than most, especially if you control the receiving address.

If the destination address is yours

In many cases, the funds are not lost. They are simply on another network than the one your wallet is currently displaying.

Step 1. Confirm which network was used

Open the transaction in a block explorer. Check which blockchain processed it: Ethereum, Arbitrum, Base, BNB Chain, Polygon, Solana, or another network. This is the network where your funds now exist.

Step 2. Switch your wallet to that network

Open your wallet. In MetaMask, click the network selector at the top and choose the correct network.

If it is not listed, add it manually using chainlist.org or through your wallet's official network setup process.

Always verify the network details before adding it. Fake network entries and phishing copies exist. Before confirming, cross-check the Chain ID against the official project documentation or chainlist.org. The Chain ID is the only reliable identifier, the network name alone can be duplicated.

Once added, switch to it. Your balance may immediately appear.

Step 3. If nothing appears, check whether the token is simply hidden

Wallets do not automatically display every token. That does not mean the token is missing.

Open the transaction in a block explorer and identify the token name and the token contract address. Then in your wallet, select Import token, paste the contract address, and confirm. The token balance often appears immediately after.

Example

You sent USDC to your own wallet address. You expected it on Ethereum. You accidentally sent it on Arbitrum. Your Ethereum wallet shows nothing. You switch to Arbitrum and import the USDC contract. Your funds appear. Nothing was recovered. They were there the whole time.

If the destination is a platform or exchange

Recovery depends entirely on the platform.

Before opening a ticket, check whether the platform officially supports that token on that network. If they do not support that combination, recovery becomes uncertain.

Then contact support and provide:

• Transaction hash (TXID)
• Network used
• Token and amount
• receiving address
• your account email or account ID.

Expect delays, possible fees, and no guarantee of success.

Case 3. Wrong amount

If you sent too little

Before sending anything additional, make sure the first transaction was correct in every other way.

In most cases, you can send a second transaction to make up the difference.
This works for wallet-to-wallet transfers. 
For exchanges or DeFi protocols, check whether the platform requires the full amount in a single transaction before sending anything additional.

If you sent too much

To a Wallet or a known recipient 
→ contact them and request a return.

To an Exchange 
→ log into your account and withdraw the excess if it has been credited.

To a DeFi protocol 
→ open the protocol interface and look for:

• Withdraw
• Claim
• Remove liquidity

You can use for example Debank (debank.com) to check whether your funds are still associated with an active position. This helps you locate funds, but it does not recover them on its own.

If no withdrawal function is available, recovery may not be possible in practice.
Before assuming the funds are permanently lost, check the protocol documentation, official support channels, or the project's community. Some protocols include withdrawal or recovery mechanisms that are not immediately visible.

Case 4. Wrong memo or destination tag

Some blockchains require an additional identifier alongside the address. This is called a memo or destination tag. It tells the platform which account to credit. Without the correct memo, the funds arrive at the platform but cannot be matched to your account.

This applies to networks such as:

• Cosmos
• XRP Ledger
• Stellar

You can inspect these transactions using dedicated explorers:

• Cosmos → mintscan.io
• XRP Ledger → xrpscan.com
• Stellar → stellarchain.io

Without the correct memo, the funds arrive, but are not credited.

What to do

Go to the platform's official support page. 
Before contacting them, gather everything in one place: 

• transaction hash
• sending address
• receiving address
• your platform account ID or email
• token
• amount
• network
• memo you used or confirmation that it was missing.

The more complete your first message, the less back-and-forth, and the faster the resolution.

Recovery is often possible, but it usually requires human intervention, so delays and fees are common.

Case 5. Sent to a DeFi smart contract

There are two distinct situations.

Sent to the wrong contract address

Recovery is unlikely. Smart contracts do not include a recovery mechanism unless one was explicitly built in.

Before accepting this outcome:

• Open the contract address in a block explorer.
• Check if it is verified. This means its code is publicly readable.
• Look for any function related to withdrawal or recovery.
• If you are unsure, use the official interface of the protocol rather than interacting directly with the contract.

If nothing is available, recovery is unlikely. Before assuming the funds are permanently lost, check the protocol documentation or official support and community channels. Some recovery mechanisms are not immediately obvious.

You interacted with the right protocol, but something went wrong

Go to the protocol's official interface.
Connect your wallet. 
Look for options such as Withdraw, Unstake, Claim, or Remove liquidity. 
If a relevant function exists, follow the interface steps to recover your position.

If nothing is available in the interface or contract, recovery may not be possible through normal user actions. Check the protocol documentation or official support and community channels before concluding the position cannot be recovered.

Case 6. Wrong token or unsupported asset

You may have sent a token that the destination does not recognise or support.

Before assuming the funds are lost, check which situation applies to you.

Situation A. The token is not visible in your wallet

This is the most common case, and it is often not a real problem.

Wallets do not automatically display every token. The token may already be in your wallet, simply not visible yet.

How to check:

1. Open a block explorer.
2. Search your wallet address.
3. Look at the token transfer section.

If the token appears there, your wallet received it. It just needs to be added manually.

How to add it:

1. Copy the token contract address from the explorer.
2. In your wallet, select Import token.
3. Paste the contract address and confirm.

The balance should appear immediately.

Example: you receive a lesser-known token on Ethereum. MetaMask shows nothing. You open Etherscan, find the token in your address history, import the contract address, and the balance appears. The funds were there all along.

Situation B. The destination does not support that token

This is a different problem. The transaction may have been processed on-chain, but the destination has no way to use or return the asset.

This happens when you send a token an exchange does not list, send an ERC-20 token to a contract that only accepts ETH, or send a token on a network the destination does not support.

Example: you send an ERC-20 token to a smart contract designed only to accept ETH. The transaction succeeds on-chain. The contract has no withdraw or recovery function for that token. The funds arrive and cannot leave.

What to do depends on where you sent the funds:

To one of your own wallets: check that you are on the correct network and that the token is imported. If yes, recovery is often possible.

To a platform or exchange: contact support. Ask whether they support that token on that network, and whether they offer recovery for unsupported deposits. Recovery depends entirely on the platform.

To a smart contract: open the contract in a block explorer and look for any of these functions: withdraw, rescueTokens, recoverERC20, sweep, or claim. If none exist, the funds are likely not recoverable in practice.

Quick recovery map

If you sent funds to a wrong address controlled by someone else, recovery is usually not possible unless you can identify and contact that person, and they agree to send the funds back.

If you sent funds to an unknown wallet and you cannot identify who controls it, the funds should be considered lost.

If you used the wrong network but the same private key controls the address, recovery may be possible by accessing that network with the correct wallet.

If you forgot a memo, tag, or reference on a platform deposit, recovery depends on the platform support process.

If you sent an unsupported token to an exchange, recovery depends entirely on whether the exchange can and agrees to retrieve it.

If you sent funds to a smart contract that was not designed to return them, recovery is usually difficult or impossible.

If you sent the wrong amount, recovery is sometimes possible, depending on who received it and whether funds remain withdrawable.