Bitcoin address validator
Parts of this address
- 1Prefix
1Fixed by the version byte 0x00 → Bitcoin pay-to-public-key-hash.
- 2Payload
A1zP1…Lmv720-byte hash of the public key: 62e907b1…8f18.
- 3Checksum
DivfNaLast 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
bitcoincash:qp3wjpa3tjlj042z2wv7hahsldgwhwy0rq9sywjpyyFormat rules
- Starts with
- 13bc1qbc1p
- Length
- 26–35 · 42 / 62
- Encoding
- Base58Check · Bech32 · Bech32m
- Checksum
- 4 bytes double SHA-256 · 6-character BCH code
- Typo check
- Full: format and checksum
- Memo / tag
- Not used
What is checked
- Legacy
1…(P2PKH, version byte 0x00) and3…(P2SH, 0x05) are Base58Check: the last 4 bytes are a double SHA-256 checksum. bc1q…is SegWit version 0 with a Bech32 checksum (BIP-173);bc1p…is Taproot with Bech32m (BIP-350). Both checksums can locate a single wrong character.- Testnet uses
tb1…,m…,n…and2…; regtest usesbcrt1….
Specification: BIP-173 (Bech32) · BIP-350 (Bech32m) · Bitcoin wiki: Base58Check
Example above: the address in the first Bitcoin block (genesis).
FAQ
How do I check if a Bitcoin address is valid?
Paste it above. The checker decodes it, verifies the Base58Check or Bech32/Bech32m checksum in your browser and names the address type. A valid result means the format and checksum hold, not who controls the address.
Which Bitcoin address types are there?
Legacy 1… (P2PKH), script 3… (P2SH), native SegWit bc1q… and Taproot bc1p…. All four can receive bitcoin; some services do not accept bc1p yet.