Menu

Crypto address checker

Checked in this browser. The address is not sent to a server.
Public examples
Valid format and checksumBitcoin · Legacy · P2PKH
Base58Check checksum matches

Parts of this address

  • 1Prefix 1

    Fixed by the version byte 0x00 → Bitcoin pay-to-public-key-hash.

  • 2Payload A1zP1…Lmv7

    20-byte hash of the public key: 62e907b1…8f18.

  • 3Checksum DivfNa

    Last 4 bytes, taken from a double SHA-256 of everything before. Base58 does not align to bytes, so the marked characters are approximate.

Details

Network
Bitcoin
Type
Legacy · P2PKH
Encoding
Base58Check
Length
34 characters · 25 bytes
Checksum
matches
Version
0x00
Hash
62e907b15c…

Watch out

  • Bitcoin Cash legacy addresses look the same (1… and 3…). Make sure the sender is sending BTC, not BCH.

Same address in another form

If this is a Bitcoin Cash legacy address, its CashAddr formbitcoincash:qp3wjpa3tjlj042z2wv7hahsldgwhwy0rq9sywjpyy
What this does not proveA valid format only means the address is well-formed. It does not show who controls it or that it is the address the recipient gave. Compare the whole address with the source and send a small test amount first.

USDT network checker

this address: no network in this list fits
NetworkAddress looks likeMemoThis address
No network fitsThis is a Bitcoin address. None of the USDT networks below uses this address format, so USDT cannot be sent to it on any of them.
T
TRONTRC-20
T… · 34 charactersNone—
E
EthereumERC-20
0x… · 42 charactersNone—
B
BNB Smart ChainBEP-20
0x… · 42 charactersNone—
S
SolanaSPL
Base58 · 32–44 charactersNone—
T
TONJetton
EQ… / UQ… · 48 charactersComment on exchanges—
P
PolygonERC-20 on Polygon
0x… · 42 charactersNone—
A
Arbitrum OneERC-20 on Arbitrum
0x… · 42 charactersNone—
A
Avalanche C-ChainERC-20 on Avalanche
0x… · 42 charactersNone—

USDT exists as a separate token on each of these networks. The address format shows which of them can receive on this address; the network selected when sending has to be one marked “Fits” — and for a 0x… address, the one the recipient named. Which networks the issuer itself lists is on the USDT contract page.

Supported networks

NetworkStarts withLengthEncodingChecksumTypo check
B
BitcoinLegacy · P2PKH
1
26–34Base58Check4 bytes · double SHA-256Full
B
BitcoinScript · P2SH
3
34Base58Check4 bytes · double SHA-256Full
B
BitcoinSegWit v0
bc1q
42 / 62Bech326 characters · BCH codeFull
B
BitcoinTaproot
bc1p
62Bech32m6 characters · BCH codeFull
Ł
LitecoinL · M · ltc1
LMltc1
34 / 43 / 63Base58Check · Bech32as BitcoinFull
D
DogecoinLegacy · P2SH
D9A
34Base58Check4 bytes · double SHA-256Full
B
Bitcoin CashCashAddr
qp
42CashAddr40-bit BCH codeFull
D
DashLegacy · P2SH
X7
34Base58Check4 bytes · double SHA-256Full
Z
ZcashTransparent · shielded · unified
t1t3zs1u1
35 / 78 / 100+Base58Check · Bech32 · Bech32m4 bytes · BCH codeFull
E
Ethereum · EVMAccount or contract
0x
42Hex · 20 bytesLetter case (EIP-55), optionalFormat · case
T
TRONAccount or contract
T
34Base58Check4 bytes · double SHA-256Full
X
XRP LedgerClassic · X-address
rX
25–35 / 47Base58Check · XRP alphabet4 bytes · double SHA-256Full
S
SolanaAccount
any Base58
32–44Base58 · 32 bytesNoneFormat only
T
TONUser-friendly · raw
EQUQ0:
48 / 66Base64url · hexCRC16 (user-friendly form)Full
A
CardanoShelley · Byron
addr1stake1Ae2DdzFF
58 / 59 / 103Bech32 · Base58 + CBOR6 characters · BCH code · CRC32Full
S
StellarAccount · muxed
GM
56 / 69Base32CRC16Full
C
Cosmos chainscosmos, osmo, …
cosmos1osmo1
45+Bech326 characters · BCH codeFull
M
MoneroStandard, subaddress, integrated
48
95 / 106Base58 · Monero blocks4 bytes · Keccak-256Full
P
Polkadot · KusamaSS58
15C–H
47–48Base58 · SS582 bytes · BLAKE2b-512Full
A
AlgorandAccount
A–Z, 2–7
58Base324 bytes · SHA-512/256Full
T
Tezostz accounts · KT1 contracts
tz1tz2tz3KT1
36Base58Check4 bytes · double SHA-256Full
K
KaspaSchnorr · ECDSA · P2SH
kaspa:qkaspa:p
61 / 63 + prefixCashAddr-style40-bit BCH codeFull
N
NEARNamed · implicit
.near
2–64Name or hexNoneFormat only
S
Sui · AptosAccount or object
0x
66Hex · 32 bytesNoneFormat only
✓ Full: format and checksum are verified in the browser– Format only: no checksum to verify, a typo cannot be detectedFormat · case: EIP-55 checksum only when written in mixed case

Same address, different network

EVM chains share one address format
One address0xdAC17F958D2ee523a2206206994597C13D831ec7

Valid on every network to the right.

E
EthereumERC-20 · recipient looks here
B
BNB Smart ChainBEP-20 · transfer was sent here
P
PolygonSeparate ledger
A
Arbitrum OneSeparate ledger
B
BaseSeparate ledger

What the format can tell

A T… address belongs to TRON and a bc1… address to Bitcoin. Sending those on another network is refused, because the address is not valid there.

What the format cannot tell

A 0x… address is valid on every EVM chain. The transfer goes through on whichever network was selected. If the recipient is an exchange that watches a different chain, the deposit is not credited automatically.

Before sending

Ask the recipient for the network name together with the address, and select the same one.

Sent asAddressFormat checkResult
T
USDT · TRC-20to a T… address
T…Valid on TRONArrivesNetwork and address match.
E
USDT · ERC-20to a T… address
T…Not an Ethereum addressRefused before sendingWallets and exchanges block it.
B
USDT · BEP-20recipient expects ERC-20
0x…Valid on both chainsSent to the other chainRecovery depends on who holds the key.

More on this: sent on the wrong network — what can be done.

No server check

Decoding and checksums run in JavaScript on this device. The page is not allowed to make any request, so none can contain the address.

No balance or owner lookup

The checker reads the characters only. It does not query a blockchain and cannot name an owner.

Works offline

Once loaded, the page keeps working without a connection.

More tools

Compare two addressesEvery differing character marked — the clipboard-malware check.Address poisoning checkFind look-alikes in a list from your history.Batch checkA whole list at once, as a table and CSV.Scan a QR codeCamera or image, decoded on this device.Convert formatsCashAddr, X-address, TON forms, EIP-55, Litecoin 3 ↔ M.Sent on the wrong networkWhat can and cannot be done, case by case.

FAQ

Is my address sent anywhere?

No. The check runs in JavaScript in your browser. The page's security policy forbids it from opening any connection (connect-src 'none'), so it could not send the address even by mistake. The address is not put in the URL and not stored.

Does “valid” mean the address is safe to send to?

No. Valid means the address is well-formed and its checksum holds. It says nothing about who controls it, and an address swapped by clipboard malware is also valid. Compare the whole address with the source and send a small test amount first.

Which network is a 0x… address on?

Every EVM chain uses the same 0x… format: Ethereum, BNB Smart Chain, Polygon, Arbitrum, Base and more. The address cannot say which one the recipient watches — ask for the network name.

Can the checker find a typo?

For formats with a checksum, yes: a mistyped Bitcoin, TRON, XRP, Litecoin or Bech32 address fails the check, and the checker points at the character that would fix it. Solana, Sui and all-lowercase EVM addresses have no checksum, so a typo there cannot be detected.

Can it show the balance or the owner?

No. That needs a request to a blockchain or a database, which this site never makes. It reads the characters only.