Catch encoding mistakes
Verify the checksum, network prefix, address family, witness version, and exact scriptPubKey before copying an unfamiliar destination into another workflow.
Tools · Privacy-first
Address & Script Inspector
Check a Bitcoin address before using it, or translate a raw output script into its recognized template and address forms. The inspector validates Base58Check, Bech32 and Bech32m checksums, identifies compatible networks, exposes witness versions and programs, and derives the exact scriptPubKey locally.
It does not query balances, transaction history, ownership, UTXO state, or a blockchain explorer. A valid checksum only proves that the address was encoded consistently; it does not prove who controls it or whether sending to it is appropriate.
Runs locally
Your address or script stays in this browser.
Local input: A Bitcoin address or scriptPubKey hex. Public address data is still kept local to avoid automatic lookup disclosure. Network effect: None when inspecting. Input is processed in this page and is not sent to BitcoinStats, a node, an explorer, analytics, browser storage, or the URL.
Address or scriptBrowser validationDecoded structure
After the page assets load, inspection continues without internet access. Inputs are not added to the URL, browser storage, or site analytics.
Address mode validates the network encoding and checksum without contacting a server.
Inspection result
Decoded structure
Exact values
Address and script data
Interpretation
What the result means
Address representations
Network-specific encodings
A scriptPubKey is network-agnostic. These addresses encode the same locking script for each Bitcoin network; shared encodings are grouped together.
Purpose and limits
Decode the representation, not the owner
Understand network ambiguity
Testnet and Signet share address encodings. Their Base58 prefixes are also shared with Regtest, so the address alone cannot always name one network.
No chain-state claim
The inspector does not prove ownership, signatures, spendability, activity, balance, history, policy acceptance, or whether a script is present in the active chain.
Parsing uses locally bundled, version-pinned @scure/btc-signer and @scure/base. Bech32 and Bech32m behavior is tested against BIP173/BIP350 vectors and script classifications are cross-checked with Bitcoin Core.