Crypto wallet address validator for 12 blockchains
Sending coins to a mistyped address is irreversible, so wallets and exchanges build a checksum into the address itself. This crypto wallet address validator recognises the format of an address, works out which blockchain it belongs to and verifies that checksum: base58check with double SHA-256 for Bitcoin, Litecoin, Dogecoin, Dash and Tron; bech32 and bech32m for SegWit and Taproot; EIP-55 letter-case checksums for Ethereum and every EVM chain; CashAddr for Bitcoin Cash; Ripple’s base58 for XRP; SS58 with blake2b for Polkadot and Kusama; bech32 for Cardano Shelley and Cosmos SDK chains; and Monero’s block-wise base58 with a Keccak checksum.
Beyond valid/invalid, it shows what the address is — legacy P2PKH, native SegWit, Taproot, a Cardano base address, a Polkadot account — and warns about classic mistakes: a Cosmos address for the wrong chain, an Ethereum address with no checksum, or a string that is really a private key.
All decoding and hashing run in your browser; no address is sent anywhere. The page is informational only and not investment advice.
How to use the Crypto Wallet Address Validator
- Paste the address into Wallet address. The result updates as you type.
- Read the badges: valid or invalid, the chain and address type, and a network flag if it is a testnet address.
- Check the details (hash, public key, witness version, prefix) and the notes, which explain any problem or ambiguity.
- Compare the first and last few characters with the source you copied from — a checksum catches typos, not a swapped clipboard.
- For many addresses switch to Bulk list, paste one per line, press Validate list and download the CSV.
Crypto Wallet Address Validator features
Twelve chains, one box
Bitcoin (incl. testnet), Ethereum and all EVM chains, Litecoin, Dogecoin, Bitcoin Cash, Tron, Solana, XRP, Polkadot/Substrate, Cardano, Cosmos SDK chains and Monero, plus Dash and Zcash transparent addresses.
Real checksum verification
Not a regex: every address is decoded and its checksum recomputed with the chain’s own algorithm (double SHA-256, bech32 polymod, Keccak-256, blake2b-512).
SegWit and Taproot aware
Witness version, program length and the bech32 vs bech32m rule from BIP-350 are enforced, so a Taproot address with the old checksum is rejected as wallets would.
Private-key detection
A Bitcoin WIF key pasted by mistake is identified and you are told to treat it as compromised.
Bulk validation with CSV
Clean up an airdrop list or a payout sheet: each line gets a status, chain, type and note.
Address formats at a glance
| Chain | Starts with | Encoding | Checksum |
|---|---|---|---|
| Bitcoin legacy / P2SH | 1 / 3 (testnet m, n, 2) | base58check, 25 bytes | first 4 bytes of SHA-256(SHA-256()) |
| Bitcoin SegWit / Taproot | bc1q / bc1p (testnet tb1) | bech32 / bech32m | 6-character polymod |
| Ethereum and EVM chains | 0x + 40 hex | hex | EIP-55 letter case from Keccak-256 |
| Litecoin | L, M, ltc1 | base58check / bech32 | as Bitcoin |
| Dogecoin | D (P2SH 9 or A) | base58check | double SHA-256 |
| Bitcoin Cash | bitcoincash:q… or q… | CashAddr (base32) | 40-bit polymod |
| Tron | T | base58check, version 0x41 | double SHA-256 |
| Solana | any base58, 32–44 chars | base58 of a 32-byte key | none |
| XRP Ledger | r | base58check, Ripple alphabet | double SHA-256 |
| Polkadot / Kusama / Substrate | 1 / C–H / 5 | SS58 (base58) | 2 bytes of blake2b-512 |
| Cardano (Shelley) | addr1 / stake1 | bech32, up to 103 chars | 6-character polymod |
| Cosmos SDK chains | cosmos1, osmo1, … | bech32 | 6-character polymod |
| Monero | 4 (subaddress 8) | Monero base58, 95 or 106 chars | 4 bytes of Keccak-256 |
What a valid checksum does and does not tell you
A checksum guards against transcription errors: a single wrong character in a Bitcoin address is caught with certainty, and in an EIP-55 address with roughly 98.5% probability. It cannot tell you that the address belongs to the person you think, or that it is not a look-alike from “address poisoning” — dust sent from an address whose first and last characters match a contact, so you copy it from your history by mistake. Verify new addresses through a second channel and send a small test first.
- Bitcoin, Litecoin and Bitcoin Cash share history, so a 3… address can be valid on more than one chain; the chain is decided by the sender’s wallet, not the address.
- An Ethereum address is the same on every EVM chain, but tokens live on one chain at a time — sending USDC on Polygon to someone expecting it on Ethereum needs a bridge, not a different address.
- Solana addresses have no checksum at all; this tool can only confirm the length and alphabet.
- XRP and many exchange deposits need a destination tag or memo in addition to the address. Omitting it is a common cause of lost deposits.
Related tools
Convert an Ethereum address to its checksummed form with the EIP-55 converter, check a seed phrase’s word list and checksum with the BIP-39 mnemonic checker (never a real one), create a payment QR with the Bitcoin QR generator, or convert fee amounts with the satoshi to BTC converter.
Crypto Wallet Address Validator FAQ
How do I know if a crypto wallet address is valid?
Paste it here. The validator decodes it with the chain’s encoding and recomputes its checksum. If the badge says valid, the address is well-formed and free of typos; if invalid, at least one character is wrong and you should re-copy it.
Can the validator tell which blockchain an address belongs to?
Usually. Prefixes and version bytes identify Bitcoin, Litecoin, Dogecoin, Tron, XRP, Monero, Cardano, Cosmos chains and Polkadot. A 0x address belongs to every EVM chain at once, and a 32-byte base58 key is most likely Solana, so the notes explain any ambiguity.
Does a valid address mean it is safe to send funds?
No. It means the characters are consistent. It does not prove ownership, the intended chain, or that the address is not an impostor. Verify with the recipient and send a small test amount first.
Why is my Ethereum address shown as valid but with a warning?
It is all lowercase or all uppercase, so it has no EIP-55 checksum. It will work, but a typo could not be detected. Use the checksummed form shown in the details.
Is it safe to paste addresses into this crypto wallet address validator?
Yes. Addresses are public and the page processes them locally; nothing is uploaded. Never paste private keys or seed phrases anywhere — if you paste a WIF key here by accident, the tool warns you and you should move the funds.
Which address types are not supported?
Stellar, Algorand, Aptos, Sui, Hedera and NEAR named accounts, Bitcoin Lightning invoices, Zcash shielded addresses and ENS names are not decoded. Unrecognised bech32 prefixes are checksum-verified but not identified.