WORLD CRYPTOCURRENCY GUIDE
Practical analysis

Sending cryptocurrency: check the asset, network and address

An address that looks right is not enough: the asset, network, destination and fees must all match.

Two network paths converging on a verified address
Educational illustration: Two network paths converging on a verified address
Short answer

Before signing, ask the recipient to confirm the asset, network and full address. Check any extra destination fields, fees and amount received. For a new destination, start with a small test and wait for receipt.

A compact home computing and network setup for a fictional full-node project, small server and laptop on a desk, no readable screens
Confirm the destination

Asset, network and address

Inspect the address

Read the whole string

Budget the costs

Balance and fees

01

Confirm the destination

Get deposit instructions directly from the recipient. The same token may exist on networks that are not interchangeable. For a service, check the networks it actually supports and any additional destination fields.

02

Inspect the address

Copy the address from a trusted source, then compare it in full in the wallet or on the signing device. An address taken from transaction history or matching only its first and last characters may be a trap.

03

Budget the costs

Check the amount sent, provider withdrawal fees and the native asset needed for network fees. If the recipient needs an exact amount, account for all costs before confirming.

04

Make a test

For a first transfer or large amount, send a small sum on the same network to the same destination. Confirm receipt with the recipient before sending the rest. The test also incurs a fee.

05

Track the outcome

Keep the transaction identifier. Check its status on an explorer for the correct network and distinguish broadcast, inclusion and service credit. If it remains pending, follow the wallet’s official procedure instead of blindly resending the amount.

06

Diagnose a pending transfer

“Processing” at a platform can precede any onchain broadcast. With a hash, inspect the correct network, transaction status and destination; without one, first ask the provider whether withdrawal was sent.

  • Chain confirmation does not prove the recipient has credited its account yet.
  • Do not send a second transfer to “unlock” the first without diagnosing it.
07

Practical case: decision and limits

A test succeeds, then a new address is supplied for the main amount. The test does not cover that change: repeat recipient, network and asset checks. An exchange may require a tag or memo despite a correct address. Copy from the official source and compare the entire address; history may contain an attacker’s lookalike.

08

A concrete verification

Get the address from the official source: unsolicited transfers can insert lookalikes into history.

09

Hypothetical case: the test used a different route

A small transfer succeeds on one network, then the main transfer is prepared on a cheaper network. The first test did not validate the second route. Compare asset, contract, network, address and any memo for both operations. Even an identical test does not establish that limits, provider processing or withdrawal conditions remain unchanged for a larger amount.

  • Retrieve destination deposit instructions in an official session, not an old message.
  • Treat a changed route characteristic as a new route to verify.
  • Keep quoted fees and actual received amount; a lower-cost promise alone is insufficient for comparison.
10

Check the transfer evidence

Keep the deposit instructions obtained through the recipient’s official channel: asset, network, full address and any memo. Compare them with the details actually signed, then inspect the transaction ID on an explorer for that network. A visible or included transaction establishes a network state; it does not by itself prove that a custodial service credited your account. Required confirmations and accepted assets depend on the receiving service.

  • Compare the complete destination and network, not just the first and last address characters.
  • Record network status and recipient account credit separately.
11

If the deposit is still missing

First check that the transaction used the correct network and that the service supports the asset. Compare any required memo or destination tag with what was sent. If the network confirms the transaction but the account is not credited, contact only the recipient’s official support with the transaction ID and relevant details; never provide a recovery phrase or private key. Do not send the amount again to “release” the first transfer. Any possible recovery depends on who controls the destination and the service’s procedures.

  • Keep the transaction ID and dated deposit instructions.
  • Reject recovery offers requesting a key or an advance payment.
Compare

Checks to make

Checks to make
TopicCheck
Confirm the destinationAsset, network and address
Inspect the addressRead the whole string
Budget the costsBalance and fees
Make a testTry a new route
Track the outcomeHash and receipt

Prepare a transfer: output and checks

Compare two fee conventions with your own numbers. All amounts must use the same unit: calculate fees paid in another asset separately.

Estimated total debit : 102
Estimated amount received : 100

Hypothetical example: sending 100 with 2 added in fees debits 102 and delivers 100; deducted fees debit 100 and deliver 98. Check variable fees, minimums and service rounding.

Checks before signing

These checks are reminders, not a safety validation. No address or key is requested; this tool sends nothing to a service.

FAQ

Frequently asked questions

Does the same 0x address work on every network?

Not necessarily. A matching address format does not mean the recipient accepts the selected network or token.

Does a small test guarantee the next transfer?

No. It reduces some destination errors, but recheck the details and network state for every send.

What if I selected the wrong network?

Stop further sends and contact the recipient or service through its official channel. Any possible recovery depends on custody and supported networks.

What if an unknown token arrives unsolicited?

Receipt alone generally does not require your signature. Do not open its description URL or sell it to unlock a claimed reward. Names, displayed values and unsolicited transfers establish neither legitimacy nor liquidity.

Does a confirmed transaction guarantee immediate credit?

No. A platform may apply its own deposit checks and conditions. Verify network, asset and service instructions, then contact official support with the transaction ID.

Verifiable sources

Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated October 23, 2026

Related terms

Address poisoning
Small transactions from a lookalike address intended to make someone copy the wrong destination from their history.
Deposit memo
Additional identifier some services require to credit a deposit to the right account; it must be copied exactly.
Network compatibility
Checking that sender and recipient use the same supported network for a particular asset.
Public address
Shareable identifier for receiving an asset on a specific network; it does not reveal the private key.

Prepare and continue reading

Useful background

  • How to choose a crypto wallet

    A crypto wallet manages the keys that authorize operations; it does not physically hold the assets. The right choice depends on use, value at risk and your ability to protect a recovery phrase without sharing it.

  • Understand crypto fees and the amount actually received

    Total cost can combine a price spread, service commission, payment, withdrawal and network fees. Always compare the amount debited with the net amount received in the same asset or currency at approximately the same time.

Continue to the next step