Sending crypto looks simple. Pick the asset. Pick the chain. Paste the address. Set the amount. Confirm. The screen says "sent" and the wallet shows a pending transaction. Most guides stop there. The cases that end in lost funds start at the boxes the click sequence does not show: the wrong chain, the missing memo, the address you pasted from your transaction history, and the fee you set too low when the mempool was on fire.
What you'll learn
What "send" and "receive" actually do on a blockchain
How to share a receive address without errors
How to send without falling into the wrong-chain trap
How to spot a poisoned address before you confirm
When a memo or destination tag is required, and what happens if you skip it
How fees and gas work, and which option to pick
What to do when a transaction is stuck or fails
What does "send" and "receive" actually mean on a blockchain?
Sending crypto broadcasts a signed transaction to the network's mempool. Validators or miners pick it up and include it in the next block. Once enough blocks have stacked on top, the transaction is irreversible. Receiving crypto means a transaction arrived at one of your addresses. Your wallet usually shows it within seconds of broadcast and confirms it after the network does.
Here is the short version of the lifecycle. You build a transaction in your wallet. The wallet signs it with your private key. The wallet broadcasts the signed transaction to peer nodes on the network. The peers gossip it to validators or miners. A validator includes it in the next block. After one confirmation, the transaction is in the chain. After more confirmations, replacing it gets exponentially harder. By six confirmations on Bitcoin or 30 on Ethereum, the transaction is practically permanent.
The "practically permanent" part is what matters for the rest of this guide. There is no chargeback. There is no "I sent this by mistake" button. The blockchain does not know who you are. It only knows the rules of the protocol and the math of your signature. So every step before you confirm matters. Once confirmed, the only paths to recovery are: the recipient sends it back, or in narrow exchange-deposit cases, support can re-credit you.
Transaction lifecycle, in order
Stage | What is happening | Where it shows |
|---|---|---|
Built | Your wallet assembles asset + amount + recipient + fee | Wallet's "review" screen |
Signed | Your private key signs the transaction | Wallet's "confirm" prompt |
Broadcast | Wallet sends signed tx to peer nodes | Tx hash exists in mempool |
Included | A validator puts it in a block | Block explorer shows "1 confirmation" |
Confirmed | More blocks stack on top | Most exchanges accept after 1-30 confirmations depending on asset |
Irreversible | Enough blocks that replacement is impossible in practice | Both sides treat as final |
For the deeper view of how the wallet builds and signs the transaction, see how crypto wallets work. For the address you are sending to or from, see what is a blockchain address.
How do you receive crypto safely?
Open your wallet. Pick the asset and chain. Tap Receive. Share the displayed address with the sender, by QR code or copy. Confirm the sender has the exact address and the matching chain. Never assume an address from one chain works on another. The sender's wallet should show the same first and last characters as yours before they confirm.
The receive side is the easier of the two. Your wallet generates a receive address (or shows a fixed one, depending on chain). On Bitcoin and Ethereum, each receive transaction usually gets a fresh address for privacy, though reusing the same address still works. On Solana, addresses are typically reused. On chains that use account models (Ethereum, Solana, BNB Chain), your address is the same whether you are sending or receiving. On UTXO chains (Bitcoin, Litecoin, Bitcoin Cash), the "address" is a destination for new outputs.
The four-step receive checklist
Open your wallet and select the receiving asset
Confirm the chain matches what the sender is sending (USDC on Ethereum is not the same as USDC on Polygon)
Share the address by QR if you can, by copy if you must, and never by typing
Verify on the sender's side that the address shown matches yours, character for character
A common confusion at this step is when the receiving asset has the same ticker on multiple chains. USDC exists natively on Ethereum, Polygon, Avalanche, Arbitrum, Optimism, Solana, and more. Same ticker, different networks. The addresses are NOT interchangeable across them. Your wallet may show the same string of characters for the receive address on three of those chains, but the funds only land on the chain you specified. If the sender picks the wrong chain, your wallet will not see anything.
How do you send crypto without a wrong-chain disaster?
Five fields matter every time you send. Asset. Network. Recipient address. Amount. Fee. The most expensive mistake is mismatching the asset and the network. USDC on Tron sent to an Ethereum-only address. BTC sent to a Bitcoin Cash address that happens to start with similar characters. USDT on BNB Chain sent to a wallet that only knows about USDT on Ethereum. The wallet does not stop you. The funds are usually unrecoverable.
Walk each field. Asset is the token or coin you are sending. Easy. Network is the chain that token lives on. This is the trap. USDT, USDC, BNB, and many tokens have versions on multiple chains. The address format may look identical (both Ethereum-style 0x addresses on EVM chains; same hex format on BNB Smart Chain, Polygon, Arbitrum, etc.) but the chains are separate. Recipient address is the long hex or alphanumeric string. Amount is what you want to send. Fee is what you pay the network to include the transaction.
Wrong-chain matrix (the common traps)
Asset | Chains it lives on | Common mistake | Outcome |
|---|---|---|---|
USDT | Ethereum, Tron, BNB Smart Chain, Solana, Avalanche | Tron USDT sent to ETH address | Funds usually unrecoverable; sometimes recoverable if both endpoints same key |
USDC | Ethereum, Polygon, Arbitrum, Optimism, Solana, Avalanche, Base | Ethereum USDC sent to Solana address | Address formats differ (hex vs base58), most wallets warn; if it goes through, usually unrecoverable |
BTC | Bitcoin, Bitcoin Cash, Bitcoin SV, Liquid | BTC sent to BCH legacy address | Both look like 1... addresses; recovery sometimes possible via private-key import |
BNB | BNB Smart Chain, BNB Beacon Chain (deprecated 2024) | BSC BNB sent to old Beacon Chain address | Recovery depends on whether Beacon Chain endpoint is still alive |
ETH | Ethereum, EVM L2s (Arbitrum, Optimism, Base, etc.) | Ethereum ETH sent to L2 address controlled by same key | Often recoverable by adding the L2 network in your wallet |
The pattern that fails: assuming "same address means same network." On EVM chains in particular, the address format is identical across Ethereum, Polygon, BNB Chain, Arbitrum, Optimism, Avalanche, Base, and any other EVM L2. The same 0x... string is "your address" on every one of those chains. The funds only exist on the chain you actually sent on. To see them, you have to add that chain to your wallet. If you sent to a smart contract on the wrong chain (a token contract address that exists on Ethereum but not on the chain you sent on), the funds are usually stuck inside the contract and unreachable.
How do you avoid pasting a poisoned address?
Address-poisoning attacks insert lookalike addresses into your transaction history. Never copy a receiving address from your past transactions. Get the address fresh from the recipient each time. Verify the full address character by character on your wallet or hardware device's screen before you confirm. Not just the first and last four. The whole thing.
Address-poisoning works like this. The attacker watches the blockchain for addresses you have used recently. They generate a new address whose first and last few characters match. They send you a small or zero-value dust transaction from that lookalike address. The dust transaction shows up in your transaction history. When you go to send funds, you look at your history, copy "the address I used last time," paste it, and confirm. The lookalike took the funds.
Independent research has tracked this attack at scale. Over the two-year period to mid-2025, researchers identified roughly 270M on-chain attacks targeting 17M victims, with at least $83.8M in confirmed losses (source: USENIX Security 2025 — Blockchain Address Poisoning). Both Ledger and Trezor have published official advisories on the attack. The fix is simple but it requires discipline at the paste moment.
Paste-safe checklist
Get the receive address from the recipient fresh, not from your transaction history
If you saved the address in your wallet's address book, confirm it has not been edited
Read the full address on your wallet or hardware device screen, character by character, against what you pasted
If anything looks off, cancel the transaction and verify again with the recipient by another channel
For large amounts, send a small test first and let the recipient confirm before you send the rest
When do you need a memo or destination tag, and what happens if you skip it?
Some chains require a memo or destination tag along with the address. XRP, XLM, BNB Beacon Chain, EOS, ATOM, and HBAR are the common ones. Most exchange deposits on these chains require the memo. The address tells the exchange which hot wallet receives. The memo tells the exchange which customer to credit. Skip the memo and your funds reach the exchange's address but get stranded without an owner.
The mechanism is the same on every chain that needs a memo. The protocol-level transaction does not require a memo. The exchange's bookkeeping at the deposit layer does. So if you are sending XRP from your self-custody wallet to your own self-custody wallet on the same chain, no memo is needed. If you are sending XRP from your wallet to your exchange account, the memo is the difference between the funds arriving in your account and the funds sitting unallocated in the exchange's omnibus address.
From Blofin's withdrawal support tickets, the single most common "where did my funds go" case is an exchange-to-exchange transfer without the destination memo. The funds reach the receiving exchange's hot wallet correctly. They sit there until a manual recovery ticket pairs them with the right user account. Recovery is possible if the receiving exchange's process is set up for it. Many smaller venues do not have that process at all.
Memo-required chains for exchange deposits
Chain | Required field name | Format |
|---|---|---|
XRP | Destination tag | Numeric, usually 32-bit unsigned integer |
XLM (Stellar) | Memo | Text or numeric ID |
BNB Beacon Chain (legacy) | Memo | Text |
EOS | Memo | Text |
ATOM (Cosmos) | Memo | Text |
HBAR (Hedera) | Memo | Text |
If the destination is an exchange, always check the deposit page for the memo requirement before sending. Major exchanges show the memo right above the address. Smaller venues sometimes bury it. If the field is shown, assume it is required.
How do fees and gas work, and which option should you pick?
Network fees pay miners or validators to include your transaction in the next block. On Bitcoin, the fee is satoshis per virtual byte (sat/vB) multiplied by transaction size. On EVM chains, the fee is gas units used multiplied by gas price, where gas price is a base fee plus a priority fee per EIP-1559. Wallets usually show fast, medium, and slow tiers. Pick fast for time-sensitive sends. Pick medium for routine. Pick slow only for non-urgent transactions that can wait.
Bitcoin fees scale with the size of your transaction in bytes. A simple one-input one-output send is around 140 vBytes. A multi-input send can be 500+. At 20 sat/vB, that one-input send costs 2,800 sats. At 100 sat/vB during a peak, the same send costs 14,000 sats. Wallets estimate the right tier based on recent block fees. The "fast" tier usually targets the next block. The "slow" tier may wait 30+ blocks (5+ hours).
EVM chains use a different model since the London upgrade (EIP-1559, source: Ethereum Improvement Proposal 1559). The base fee is set by the protocol and burned. The priority fee (tip) is your bid to validators. Total cost is gas units × (base fee + priority fee). A simple ETH transfer is 21,000 gas units. A token transfer is 50,000-65,000. A complex DeFi transaction can be 200,000+. The wallet's "fast/medium/slow" toggle adjusts the priority fee.
Fee-tier decision table
Tier | When to pick it | Bitcoin behavior | EVM behavior |
|---|---|---|---|
Fast | Time-sensitive (arbitrage, exchange deposit before deadline) | Next-block target | High priority fee; 12-30 second confirm |
Medium | Routine sends (paying someone, moving to cold storage without rush) | 3-6 block target (30-60 min) | Low priority fee; 30-90 second confirm |
Slow | Background sweeps, non-urgent transfers | 30+ block target (5+ hours) | Minimal priority fee; can wait minutes-hours during congestion |
The "stuck transaction" pattern usually starts with a slow-tier fee picked during a fee spike. Your transaction gets stranded behind higher-fee transactions in the mempool. The fix is at the next H2.
What do you do when a transaction is stuck or fails?
Check the explorer first. If the transaction is in the mempool but not confirmed, you can usually replace it with a higher-fee version. Bitcoin calls this replace-by-fee (RBF, source: Bitcoin Improvement Proposal 125). EVM wallets call it fee-bump or speed-up. If the transaction confirmed but the recipient says they did not receive it, you sent to the wrong chain or skipped a required memo. Open a support ticket with the receiving exchange or recipient and include the transaction hash.
The pattern we see during EVM gas-price spikes is users sending with the wallet's default fee, then panicking when the transaction sits in the mempool for an hour. The fix is fee-bumping (replace-by-fee on Bitcoin, or simply replacing the pending transaction with a higher fee on EVM chains) from inside the same wallet. The pattern that ends up in tickets is users sending the transaction a second time from scratch and double-paying.
Decision tree for a stuck or failed transaction
What happened | Where it shows | What to do |
|---|---|---|
In mempool, not confirmed | Explorer shows "pending" or "unconfirmed" | Fee-bump or RBF from the wallet that sent it |
Confirmed, recipient says missing | Explorer shows "1+ confirmations" | Check chain, check memo, contact recipient with tx hash |
Confirmed to a wrong-chain address you control | Explorer on the chain you actually sent on shows it landed | Add the receiving network in your wallet, use the same private key |
Sent to a contract on the wrong chain | Explorer shows it went to a contract address | Usually unrecoverable; document tx hash and contact the wallet's support |
Sent to a stranger's wrong address | Explorer shows it landed somewhere you do not control | Usually unrecoverable; if you suspect a scam, report to your local authorities |
For wrong-chain cases on EVM chains where you control both ends with the same private key, the funds are usually visible after you add the receiving network in your wallet. They were always there on that chain. The wallet just was not showing that chain by default. For wrong-chain cases that crossed protocol boundaries (Bitcoin to Ethereum, or Solana to BNB Chain), recovery depends on the receiving endpoint and is usually not possible.
If the stuck or failed transaction involves an exchange deposit, the receiving exchange's support team is the next step. Provide the transaction hash, the destination address, the asset, and the chain. Memo-omission cases usually have a process. Wrong-chain cases sometimes do, depending on the exchange and the chains involved. For sends to a hardware wallet you control, see how to set up a hardware wallet and hardware wallet guide for the verification discipline before the next send.
Frequently asked questions
How long does a crypto transaction take?
Bitcoin produces a block every ten minutes on average. Most exchanges credit Bitcoin deposits after one to three confirmations, so the practical wait is 10-30 minutes. Some require six confirmations for large amounts. Ethereum produces a block every 12 seconds, but exchanges typically require 12-32 confirmations for finality (2-6 minutes). Layer-2 chains like Arbitrum, Base, and Optimism finalize in under a minute. Times stretch during network congestion. The wallet's "pending" status means your transaction was broadcast. The explorer's "confirmed" status is what receivers count.
Why are crypto fees sometimes so high?
Fees rise with network demand. When many users compete for limited block space (NFT mints, market crashes, popular token launches), the priority-fee auction pushes the average fee higher. Bitcoin and Ethereum see the biggest spikes. Layer-2 chains and lower-demand chains (Solana, Avalanche, Polygon) stay cheap most days. The 2025 Bitcoin halving and Ethereum's December 2025 Fusaka upgrade have both shifted fee patterns again. Check current rates on a fee estimator like mempool.space or etherscan.io before sending large amounts.
Can I cancel a crypto transaction after sending?
Only before the first confirmation, and only if your wallet supports replacement. On Bitcoin, replace-by-fee (RBF) lets you broadcast a higher-fee version of the same transaction that displaces the pending one. On EVM chains, you submit a new transaction with the same nonce and a higher gas price. Most wallets expose this as a "speed up" or "cancel" button. Once a transaction confirms, it is permanent. There is no chargeback mechanism and no central authority that can reverse it.
What if I send to the wrong address?
Recovery depends on who controls the receiving address. If you sent to your own wrong address (a typo on an address that happens to be valid), open the receiving wallet and check. If you sent to a stranger's address, recovery is generally impossible. If you sent to an exchange deposit address that does not match your account, the exchange may help if the asset is supported, the chain is supported, and your KYC matches. Open a support ticket with the transaction hash, asset, chain, and timestamp. Speed matters because some exchanges can only recover before the funds are swept to cold storage.
What if I send the wrong network?
Most cases are unrecoverable. The narrow exception is EVM-to-EVM sends where you control both endpoints with the same private key. USDC sent on Polygon to a "Polygon address" that is also your Ethereum address can usually be accessed by adding Polygon to your wallet. USDT or USDC sent to a smart contract on the wrong chain is usually permanent because the contract on that chain does not know what to do with the asset. Document the transaction hash and contact the receiving wallet's or exchange's support immediately. Speed matters again.
Do I always need a memo or destination tag?
No. Most chains do not use memos. The chains that require them for exchange deposits are XRP (destination tag), XLM (memo), BNB Beacon Chain (memo, deprecated), EOS (memo), ATOM (memo for most centralized exchanges), and HBAR (memo). Self-custody-to-self-custody on these chains usually does not need a memo. The requirement lives at the exchange's bookkeeping layer, not the protocol. If the destination's deposit page shows a memo field, assume it is required and copy it exactly.
What is the safest way to send a large amount?
Three steps. Send a small test first (around $10-$50, enough to cover fees). Wait for the test to land on the receiving side. Then send the full amount. If you have a hardware wallet, use it for signing and compare the destination address character by character on the device's own screen. Never paste an address you copied from a recent transaction. Confirm with the recipient by a separate channel that they got the test before you send the rest.
Researched and written by the Blofin Academy editorial team with AI-assisted drafting. Primary sources include the Bitcoin Improvement Proposal 125 (replace-by-fee), the Ethereum Improvement Proposal 1559 (gas mechanism), the USENIX Security 2025 research on address poisoning, and the published advisories from Ledger and Trezor. All facts independently checked against cited sources current as of May 2026.
This article is educational and does not constitute financial advice. Cryptocurrency transactions are irreversible. The reader retains full responsibility for asset selection, network selection, address verification, and fee setting. Specific behaviors differ between blockchains, wallets, and exchanges. Refer to the wallet's or exchange's official documentation for product-specific menu navigation.