Crypto address and transaction checker
Paste an address or a transaction ID: the tool identifies the network and format, verifies the checksum to catch typos, then suggests the right block explorer. The analysis runs in your browser.
Updated · Method and sources
Complementary tools
Tools often used with Crypto address checker
Tools in the same category
List of tools similar to Crypto address checker
Popular tools
List of popular tools related to Crypto address checker
Related articles
Articles related to the tool Crypto address checker
Checking a crypto address before sending
A crypto transaction cannot be reversed: funds sent to the wrong address or on the wrong network are usually lost. Most address formats include a checksum that catches typos; this tool verifies it, but it cannot know who owns an address.
How to use it
- Paste the address or transaction ID into the field (no spaces).
- Read the verdict: network identified, format, checksum correct or not.
- Read the notes about the network, especially for tokens that exist on several blockchains (USDT, USDC…).
- If needed, open the suggested block explorer to see the balance or confirmations.
Recognising an address by its prefix
| Starts with | Network and format |
|---|---|
1… | Bitcoin Legacy (P2PKH) |
3… | Bitcoin P2SH (multisig, nested SegWit) |
bc1q… | Bitcoin native SegWit |
bc1p… | Bitcoin Taproot |
0x… (42 characters) | Ethereum and EVM-compatible networks (BNB Chain, Polygon, Arbitrum, Base…) |
L…, M…, ltc1… | Litecoin |
D… | Dogecoin |
T… | TRON |
| 32 to 44 Base58 characters | Solana |
The network trap
The same 0x… address is valid on Ethereum, BNB Chain, Polygon and every EVM network: the checksum does not tell you which one to use. A stablecoin such as USDT exists on several networks (ERC-20 on Ethereum, TRC-20 on TRON, BEP-20 on BNB Chain…): in the sending app, choose the same network as the one given by the recipient.
What the check cannot detect
- A swapped address: some malware replaces the address copied to the clipboard with a scammer’s address, which is perfectly valid. Compare the first and last characters with those given by the recipient.
- A “poisoned” address: a scammer sends a zero-value transaction from an address that looks like your contact’s, so that it shows up in your history. Never copy an address from your history.
- The right recipient: no format check replaces confirmation through another channel, or a small test transfer.
Frequently asked questions
Can a valid address still be wrong?
Yes. The checksum catches typos, not an address replaced by another valid address. Check the start and end of the address with the recipient.
Why is an all-lowercase Ethereum address not verified?
The EIP-55 checksum is carried by the mix of upper and lower case letters. An all-lowercase address still works, but a typo in it would not be detected.
Does the tool send the address anywhere?
No: the analysis runs in your browser. If you click a block explorer, that site receives the address or hash in order to display it.
How can I tell whether a transaction is confirmed?
Paste its ID (hash), then open the network’s block explorer: it shows whether the transaction is pending or included in a block, and the number of confirmations.
How it is calculated
The tool applies the published rules of each format, without querying the blockchain.
- Bitcoin, Litecoin, Dogecoin, TRON (Base58Check): the address is decoded, then its last 4 bytes are compared with the start of the double SHA-256 of the rest; the first byte gives the network and address type.
- SegWit and Taproot (Bech32, Bech32m): checksum and rules of BIP-173 and BIP-350 (version 0 in Bech32 with a 20- or 32-byte program, later versions in Bech32m).
- Ethereum and EVM networks: 40 hexadecimal characters after 0x; if the address mixes upper and lower case, the case is compared with the EIP-55 checksum (Keccak-256).
- Solana: 32-byte Base58 public key (transaction signature: 64 bytes); this format has no checksum.
- Transaction hash: 64 hexadecimal characters (Bitcoin, Litecoin, Dogecoin, TRON) or 0x followed by 64 characters (EVM networks); a hash has no checksum.
A valid format proves neither that the address has been used, nor that it belongs to the intended recipient, nor that a transaction is confirmed: only a block explorer shows that.
Official sources
- BIP-173 – Base32 address format (Bech32) for SegWit
- BIP-350 – Bech32m for SegWit version 1+ (Taproot)
- EIP-55 – Mixed-case checksum address encoding
Updated
Indicative estimate: only the figure from the relevant authority or professional is binding.
Please note: This calculation tool is for information only: its results are neither investment advice nor tax advice. Crypto-assets are volatile and the capital invested is not guaranteed. The prices shown may differ from the price you get on an exchange.