How to Check a Crypto Wallet Address Before Sending

Before sending crypto, verify more than the string of letters and numbers. A safe transfer depends on matching the destination address to the recipient, blockchain, asset and any required memo or tag. An address can be correctly formatted but still belong to a scammer, a different wallet or an unsupported network.

Use this checklist before approving a transfer:

1. Confirm the recipient. Get the address from the intended person or service using a channel you already trust.
2. Confirm the network. Make sure the sending and receiving services support the same blockchain and token version.
3. Compare the full address. Don’t rely on a few characters at the beginning and end.
4. Check for a memo, tag or payment ID. Include it exactly if the recipient requires one.
5. Review the wallet’s final confirmation screen. Check the destination, network, asset and amount before signing.
6. Consider a test transfer. For a large payment or an unfamiliar destination, send a small amount first if fees and minimums make that practical.

The checks below explain how to do each step and what they can—and cannot—prove. No format checker or blockchain explorer can guarantee that an address is controlled by the person you intend to pay.

Start by obtaining the address from the recipient through a trusted route: for example, ask them directly in a conversation you already use, or open the deposit screen inside the official app or service you intended to use. If an address arrives in an unexpected message, verify it through a separate, known channel. A message account or email can be compromised, and a scammer may impersonate a colleague, support agent or business.

When sending to an exchange or other custodial service, sign in independently through its official app or saved entry point and find the deposit instructions for the exact asset. Do not rely on a search advertisement, unsolicited message or screenshot alone. Check that the deposit address is current and that the service accepts deposits on the network you plan to use.

For a person’s self-custody wallet, ask them to share the address directly from their wallet and confirm the network. Some wallets can generate a different receiving address for privacy; that is not automatically suspicious. The recipient must still confirm that the address is theirs and suitable for the intended asset.

Never share your seed phrase, recovery phrase or private key to “verify” an address. A legitimate sender needs a public receiving address, not control of your wallet. Anyone asking for secret recovery information is asking for the ability to take your funds.

A cryptocurrency address has a network-specific format. Some networks use hexadecimal strings, others use different character sets or prefixes, and some formats include checksums that help detect certain typing mistakes. A format or checksum check is useful for catching an invalid string, but it cannot establish that the address belongs to the intended recipient.

If you must type an address, copy it from the recipient’s wallet or official deposit page, then compare the pasted result with the original. Check the beginning, the ending and several characters in the middle. For a long address, use a wallet or service that displays the full destination clearly; a shortened address is not enough to verify every character.

You can also use a reputable address-format checker for the relevant network. Treat its result as a syntax check only. It cannot tell whether the owner is trustworthy, whether a token is supported, or whether the destination is the one you meant to pay. Avoid pasting sensitive information into unknown websites; a public address is not a secret, but your browsing and transaction details may still be private.

If a wallet reports that an address is invalid, stop rather than trying random edits. Ask the recipient to provide it again and confirm the network. Do not remove prefixes, change characters or convert an address with an unfamiliar tool unless the recipient’s official instructions explicitly require it.

The network is the blockchain on which a transaction is sent; the asset is the coin or token being transferred. A token with the same name or ticker can exist on multiple chains, and a receiving service may support it on some networks but not others. The sender’s network selection must match a route the recipient can receive and access.

For example, don’t assume that choosing a familiar token name automatically selects the right network. Read the deposit instructions or ask the recipient which network to use. Then check the network label in both the sending wallet and the receiving service before you confirm. If the two sides describe the network differently or the supported options are unclear, pause and ask the service’s official support channel.

Also check whether you are sending the native coin or a token representation. The address might look compatible while the receiving service does not support that specific asset on that chain. A transfer sent on an unsupported network may not appear in the recipient’s account, and recovery may be difficult or unavailable.

Do not infer compatibility from the address alone. Similar-looking addresses can be used across networks, and an address accepted by a wallet does not prove that a particular exchange, app or recipient can process the transaction. Confirm all three items together: the destination, the network and the exact asset.

A crypto address is often copied and pasted, which makes clipboard tampering a serious risk. Malware can replace a copied address with one controlled by an attacker. The replacement may resemble the intended address, so glancing only at the first and last characters can miss the change.

After pasting, compare the entire address with the original shown by the recipient. Look for differences in the middle as well as at the ends. If you use a QR code, scan it with the wallet’s own scanner and review the decoded destination on the wallet’s confirmation screen; a QR code is simply another way to encode data and can also point to the wrong address.

Be alert to address-poisoning attempts. An attacker may send a tiny transaction from an address that looks similar to one you have used before, hoping you will copy it from your transaction history next time. Don’t select a destination just because it appears in recent activity. Retrieve the correct address from the recipient again and compare it in full.

If your pasted address changes unexpectedly, stop. Don’t keep retrying on the same potentially compromised device. Use a trusted, updated device and verify the address with the recipient through another channel. Never approve a transaction just because the wallet displays a familiar name or icon; review the actual destination details.

Some networks or services require extra destination information, such as a memo, destination tag or payment ID. This is separate from the wallet address and helps a custodial service credit a deposit to the right account. If the deposit instructions show a required memo or tag, copy it exactly and check that it appears in the transaction form before sending.

If the service says a memo is optional, follow its current instructions rather than guessing. If you are sending to a personal wallet and the recipient says no memo is needed, don’t add one from an unrelated transaction. The receiving system determines which extra fields are required.

Confirm the amount, asset and destination on the final review screen. Check the network fee and any minimum deposit or withdrawal amount shown by the sending or receiving service. Fees can change, so use the current amount displayed in your wallet rather than relying on an old estimate. Make sure you have enough of the required network fee token if the wallet needs one.

A final screen is a last chance to catch a mismatch, not a substitute for verifying the address earlier. Read every field: destination, network, token, amount and memo or tag. If a wallet shows only a shortened address, open the details or use a wallet that lets you inspect the complete destination before signing. Cancel if any field is unexpected or unclear.

A small test transfer can be sensible when the amount is large, the recipient is new, or you are using a network for the first time. Send only an amount you can afford to lose if something goes wrong. Wait for the transaction to confirm, then ask the recipient to verify that it arrived in the correct account or wallet before sending more.

A test is not a guarantee. It can confirm that one transfer reached a destination, but it does not prove that a later transaction will use the same address, asset or network. Recheck the details for the main transfer; don’t assume the wallet retained the correct destination. Also account for network fees and any minimum deposit requirement, which may make a very small transfer unsuitable.

For a familiar recipient and a low-value payment, a test transfer may cost more than it helps. Use judgment, but never skip address and network checks because you sent to that recipient before. A compromised account or replaced address can change the risk.

If the test does not arrive, do not send the balance to “fix” it. Check the transaction status in the wallet and, if appropriate, a reputable block explorer for the correct network. Contact the receiving service through its official support channel, sharing only the transaction details it needs. Never give support staff a recovery phrase or private key.

A block explorer can help you check whether a transaction was broadcast or confirmed and whether an address has activity on a particular network. Search only for the correct chain and compare the transaction hash and destination with your wallet’s record. An explorer can also help distinguish a pending transaction from one that has been included in a block, though confirmation times vary by network.

Explorer data has limits. An address label or transaction history does not reliably prove a person’s identity or that the address belongs to a particular company. Some services use many deposit addresses, and public activity can be incomplete or difficult to interpret. A clean-looking history does not mean an address is safe; a high-risk flag is also not, by itself, proof of wrongdoing.

Address-screening services may identify links to reported scams, sanctions, illicit markets or other risk categories. Their coverage can be incomplete, their labels can be mistaken, and a new or rarely used address may have little information. Treat a warning as a reason to pause and investigate, not as a definitive verdict. Don’t treat a lack of warnings as a guarantee.

Most importantly, an explorer cannot undo a transfer or verify the recipient’s claim that they own an address. Use it as one supporting check after confirming the destination through a trusted channel. Never send money to test whether an address is “clean.”

If you notice a mistake before signing, cancel the transaction and start again with details confirmed by the recipient. If the transaction has already been broadcast, check its status in your wallet. Some unconfirmed transactions may be replaceable under network-specific conditions, but this is not guaranteed; don’t follow instructions from strangers who claim they can reverse it.

Once a transfer is confirmed, crypto transactions generally cannot be reversed by the sender. If you sent to an exchange or custodial service, contact its official support team promptly and provide the transaction hash, asset, network and destination. Recovery depends on the service’s policies and technical ability; it is not assured. If you sent to a self-custody address, contact the owner if you can identify them, but the blockchain itself cannot compel a return.

Be especially cautious of recovery scams. A person who contacts you claiming to be a hacker, investigator or support agent may promise to retrieve funds in return for an upfront payment, remote access or your recovery phrase. Do not pay or disclose secrets. Preserve messages and transaction details, secure any accounts that may be compromised, and report suspected fraud to the relevant platform or authorities in your jurisdiction.

The best protection is prevention: confirm the recipient independently, compare the complete address, match network and asset, include required tags, and review the final wallet screen before signing.