Cryptocurrency Address Format Recognition Matrix
reference
Core idea
An address prefix narrows the possibilities. It never settles the question. The single most consequential case of this is 0x: every EVM-compatible network shares the same 42-character hexadecimal format, so the address alone cannot tell you which chain the activity happened on, and getting that wrong means analysing the wrong ledger.
Components
| Chain | Prefix | Typical length | Encoding | Note |
|---|---|---|---|---|
| Bitcoin (legacy, P2PKH) | 1 | 26 to 35 | Base58 | Older format, still common |
| Bitcoin (P2SH) | 3 | 26 to 35 | Base58 | Multisignature and script-based |
| Bitcoin (Bech32 / SegWit) | bc1 | variable | lowercase alphanumeric | Modern format |
| Ethereum | 0x | 42 | hexadecimal | Shared with every EVM chain below |
| BNB Smart Chain | 0x | 42 | hexadecimal | Identical format to Ethereum |
| Polygon | 0x | 42 | hexadecimal | Address alone does not identify the chain |
| Avalanche (C-Chain) | 0x | 42 | hexadecimal | Ethereum-compatible on C-Chain |
| Arbitrum | 0x | 42 | hexadecimal | Ethereum Layer-2 |
| Optimism | 0x | 42 | hexadecimal | Ethereum Layer-2 |
| Base | 0x | 42 | hexadecimal | Ethereum Layer-2 |
| Tron | T | 34 | Base58Check | Very common in stablecoin cases |
| Solana | none | 32 to 44 | Base58 | No fixed prefix, verify on an explorer |
| Litecoin | L, M, ltc1 | variable | Base58 or Bech32 | Bitcoin-like, verify the address type |
| Dogecoin | D | 34 | Base58 | Common in retail fraud and payment cases |
| Monero | 4, 8 | approx. 95 | privacy-focused | Limited chain transparency, different discipline |
| XRP Ledger | r | variable | Base58 | Destination tags can be operationally significant |
Lengths are approximate and vary by address type and encoding. Validate with a tool, never by counting characters.
Quick lookup by first character: 1, 3, bc1 to Bitcoin. 0x to Ethereum or any other EVM chain. T to Tron. r to XRP Ledger. D to Dogecoin. L, M, ltc1 to Litecoin. 4 or 8 to Monero. No obvious prefix with Base58 to Solana.
When to use
The moment an address arrives from a victim, a referral, a screenshot, or a tip, before opening any explorer. Also whenever a trace crosses into an unfamiliar chain.
Avoid when
Do not treat this as verification. The standing pitfalls: assuming every 0x address is Ethereum, picking the wrong explorer as a result, ignoring destination tags or memos where the chain requires them, treating a smart contract address as a user wallet, and applying transparent-chain tracing methods to a privacy coin. Two addresses with the same format on different networks are not the same activity.
Example
A referral supplies a 0x address and the phrase “sent USDT”. That address format is consistent with Ethereum, BNB Smart Chain, Polygon, Base, Arbitrum, Optimism, and Avalanche C-Chain, and USDT is issued on several of them. The address establishes nothing about which chain to open. The transaction hash, or the victim’s exchange withdrawal record, is what resolves it.
Related
Blockchain Network Comparison Matrix · Token Standard Quick Reference · Wallet Type Identification Matrix · Address Poisoning Attack · Address View vs Contract View on a Block Explorer · EVM Multi-Chain Tracing Essentials · Blockchain Explorer Review Procedure · Decoding a Cross-Chain Destination Address from Input Data