What is HexoRama?
HexoRama is a client-side debugger for Bitcoin, Lightning, Ethereum, Solana, XRP Ledger, Stellar, USDT, and BNB address or payment-request formats. It validates supported encodings and provides a visual breakdown of components such as prefixes, checksums, tags, memos, invoice fields, and encoded data.
Try it out – click any address to analyze:
Use the Share command after decoding to create a route-specific link. A shared result still reports format checks only; it is not a recipient endorsement.
Local Parsing
Address and invoice parsing runs in your browser.
Instant Results
No blockchain lookup is required.
Developer Friendly
Detailed structure breakdowns.
Supported Address Formats
Bitcoin (BTC)
- • P2PKH – Legacy addresses (1...)
- • P2SH – Script hash addresses (3...)
- • Bech32 – Native SegWit (bc1q...)
- • Bech32m – Taproot (bc1p...)
- • Testnet – All formats (m/n..., 2..., tb1...)
Supports structural checks for common mainnet and testnet formats without querying a Bitcoin node or explorer.
Lightning
- • BOLT11 – Mainnet, testnet, and regtest invoice structure
- • Invoice fields – Amount, expiry, payment hash, and description
- • Optional fields – Route hints and fallback addresses
- • Payment URI –
lightning:wrappers
Decoding an invoice does not prove that it is payable, that the recipient is trusted, or that a route exists.
Ethereum (ETH)
- • Hex structure – 20-byte addresses with a 0x prefix
- • EIP-55 – Mixed-case checksum validation
- • EIP-1191 – Chain-specific checksums (RSK)
- • Known contracts – Static labels for selected addresses
- • EIP-681 – Payment URI parsing
Address format alone cannot distinguish an externally owned account from an unknown contract. Confirm current bytecode and account state with a trusted explorer or node.
Solana (SOL)
- • Public keys – Base58 values that decode to 32 bytes
- • Curve note – On-curve and off-curve address classification
- • Payment URI –
solana:request parsing
A structurally valid public key is not proof that an account exists, holds SOL or tokens, or belongs to the intended recipient.
XRP Ledger
- • Classic addresses – r-address checksum validation
- • X-addresses – Embedded destination tag inspection
- • Payment URI –
xrp:request parsing
The decoder can expose a destination tag but cannot determine whether a recipient requires one.
Stellar (XLM)
- • Accounts – G-address checksum validation
- • Muxed accounts – M-address decoding and base account extraction
- • Memos – ID, text, hash, and return types
- • SEP-7 –
web+stellar:payrequest parsing
A valid account or memo format does not confirm that the destination exists or that a memo is required.
Tether (USDT)
- • EVM – Shared 0x format used on Ethereum, BNB Smart Chain, and other networks
- • TRC-20 – Tron Network (T...)
- • SPL – Solana (Base58, 32-44 chars)
- • Omni – Legacy Bitcoin address format (1..., 3...)
An address can match more than one network format. Tether ended direct issuance and redemption on Omni, while transfers may depend on third-party infrastructure. Confirm the network and current token contract separately.
BNB Chain (BNB)
- • BEP-20 – BNB Smart Chain token standard (0x...)
- • BEP-2 – Retired BNB Beacon Chain format (bnb1..., tbnb1...)
- • EIP-55 – Mixed-case checksum for BEP-20
- • Known contracts – Static labels for selected addresses
BNB Beacon Chain was shut down in December 2024. BEP-2 checks are retained for historical format inspection and do not show whether assets are transferable or recoverable.
What Validation Cannot Prove
HexoRama checks supported syntax, encodings, checksums, and embedded fields. It does not confirm ownership, account existence, balance, token holdings, contract bytecode, the intended network, recipient identity, or whether a payment is safe to send.
Known-address labels are static reference data and can become outdated. Verify live state with an official wallet, a trusted block explorer, or your own node before moving funds. Browser extensions, the device, and third-party links remain outside this tool's security boundary.
Learning Resources
Want to dive deeper into how cryptocurrency addresses work? Check out these resources:
Bitcoin
Bitcoin Wiki: Address
Comprehensive guide to Bitcoin address formats
BIP-173: Bech32
Technical specification for SegWit address encoding
BIP-350: Bech32m
Taproot address encoding (Bech32 modified)
Ethereum
Ethereum.org: Accounts
Official documentation on Ethereum accounts and addresses
EIP-55: Mixed-case Checksum
Ethereum address checksum encoding standard
EIP-1191: Chain-Specific Checksum
Chain ID in checksum calculation (RSK and others)
Known contracts: HexoRama displays static labels for selected Ethereum contracts. An unlabeled address may still be a contract, and every label should be confirmed against current on-chain data.
USDT (Tether)
Tether Transparency
Official Tether transparency page and reserves information
ERC-20 Token Standard
Technical standard for fungible tokens like USDT on Ethereum
Solana SPL Token
Solana Program Library token standard documentation
USDT on Etherscan
View USDT ERC-20 contract and transactions on Ethereum
Note: USDT exists on multiple networks with different address formats: ERC-20/BEP-20 (0x prefix, 42 chars, EIP-55 checksum), TRC-20 (T prefix, 34 chars, Base58Check), SPL (32-44 chars, Base58, no checksum), Omni (legacy 1/3-prefixed Bitcoin addresses). Tether no longer directly issues or redeems USDT on Omni. Always confirm the network, token contract, and current transfer support before sending.
BNB Chain
BNB Chain Official
Official BNB Chain website and documentation
BEP-20 Token Standard
Technical specification for tokens on BNB Smart Chain
BEP-2 Token Standard
Historical specification for the retired BNB Beacon Chain
BscScan Explorer
BNB Smart Chain block explorer for transactions and contracts
Note: The decoder recognizes one active and one historical BNB address family:
BEP-20 (BNB Smart Chain) uses EVM-compatible 42-character hexadecimal strings starting with 0x.
Historical BEP-2 addresses use Bech32 encoding starting with bnb1 or tbnb1 (testnet).
BNB Beacon Chain shut down in December 2024; recognizing a BEP-2 string does not mean funds can be transferred or recovered.