Private Key Tools

1JSGjMcK6Mp…XeL1SNXjd — P2PKH (Pay to Public Key Hash) — Bitcoin address inspector

Paste any Bitcoin address: this page validates it, names its exact type, rebuilds the script it stands for, works out which other addresses share its key — and then reads its balance and transaction history from public explorers.

Privacy notice. Address validation is done entirely on this server and sends nothing anywhere. On-chain lookups do not: the summary and transaction table below are fetched by this server from public block explorers, which means both this server and that explorer learn which address you asked about. Set the on-chain option to “No” to keep the query completely local.
Any standard form works: 1…, 3…, bc1q…, bc1p…, plus the testnet m…/n…/2…/tb1… variants. Case does not matter for Base58, and bech32 addresses may be all-lower or all-upper — but not mixed.
Turns the server-side explorer lookups on or off. Validation, type detection and sibling derivation always work either way.
1–50.

Result

computed server-side on this host

Validation

Everything in this section is computed from the string itself, with no network access.

✓Verdict
VALID — a well-formed P2PKH (Pay to Public Key Hash)
Encoding family
Base58Check
Character length
34 characters
Chain
Bitcoin
Network
Mainnet
P2PKHAddress type
P2PKH (Pay to Public Key Hash)

Structure

What the string literally contains, byte by byte.

Checksum characters
NXjd
The last 4 Base58 characters. They encode the first 4 bytes of SHA256(SHA256(payload)).
Version byte
0x00 (0)
One byte that selects both the chain and the script type. It is covered by the checksum, so changing it invalidates the whole address.
Payload (version + hash)
00bf41ab17d28097ab5fb96ff94b7ac1a63f288a49
hash160 / commitment
bf41ab17d28097ab5fb96ff94b7ac1a63f288a49
What these 20 bytes are depends on the type: hash160(pubkey).
scriptPubKey
76a914bf41ab17d28097ab5fb96ff94b7ac1a63f288a4988ac
The actual output script this address stands for — 25 bytes. This, not the address, is what the blockchain stores.
Readable script
OP_DUP OP_HASH160 <bf41ab17d28097ab5fb96ff94b7ac1a63f288a49> OP_EQUALVERIFY OP_CHECKSIG

Sibling addresses — the same key, other scripts

P2PKH and P2WPKH both commit to hash160(pubkey), so each determines the other — and both determine the P2SH-P2WPKH form. These six addresses are all controlled by the same private key.

MP2PKH · mainnet · this address
MP2SH-P2WPKH · mainnet
TP2SH-P2WPKH · testnet

Snapshot record — from this site’s own database

A frozen historical balance from the bitcoin.tsv snapshot (content date ≈ 2026-01-28), stored locally in MySQL. No network access is involved, so this row is available even when the explorers are not.

₿Snapshot balance
35.28684231 BTC
Value in the snapshot, not the current balance. Compare it with the live figures below.
Type in snapshot
P2PKH (1…)
Rank by balance
#75,101 of 57,990,927 addresses

On-chain data — fetched by this server from public explorers

This part is a third-party claim, not a computed fact. The explorer that answered is named in every row below.

Ever used?
YES — this address has activity
₿Confirmed balance
35.28684777 BTC
Sum of unspent outputs in blocks. Bitcoin has no balance field — this is computed.
Unconfirmed balance
0.00000000 BTC
Net effect of transactions still in the mempool. It can vanish if a transaction is replaced or evicted.
Total received
35.28684777 BTC
Total spent
0.00000000 BTC
Transactions
338 confirmed, 0 pending
Unspent outputs (UTXOs)
338
How many separate coins this address holds. Every one of them becomes an input the next time the address spends, which is why a fragmented address costs more to spend.
Balance check
35.28684777 = 35.28684777 − 0.00000000
Explorer: https://blockstream.info/api · queried 2026-11-21 02:36:04 UTC

Activity window (from the listed transactions)

Most recent activity
2026-05-22 21:51:58 UTC
Oldest of these
2012-09-22 21:01:38 UTC
Chain tip
976827
Confirmations are computed against this height; a reorg below it can change them.
Public key revealed on chain?
NOT in these transactions
Spending publishes the public key in the input (scriptSig or witness). Until then a P2PKH/P2WPKH address is protected by the hash alone, which also means it is the form least exposed to a future quantum attack.

Transaction history — 25 of 338 shown

These are the newest 25 transactions, written from this address’s point of view.

TransactionTime (UTC)Conf.DirectionAmount (BTC)FeevBytesCounterparties
7abf248339…7f7e817abf248339bbfddcc50d…2026-05-2221:51:5826254height 950574in+0.00000546in 0.00000546 / out 0.000000000.0004137613,789.313871 B / 55157 WUbc1q0guz3a46dm…edxzj 0.014273921 output(s) with no address (data carrier / non-standard)
03919c4112…98452103919c41123f140abe2b…2025-07-3019:34:2768975height 907853in+0.00000548in 0.00000548 / out 0.000000000.00001140227.3309 B / 909 WUbc1qjr8h996l9p…rutt4 0.000028391 output(s) with no address (data carrier / non-standard)
396d7db2fb…630735396d7db2fbd7ffa7564e…2021-01-0113:31:13312830height 663998in+0.00000547in 0.00000547 / out 0.000000000.0013583715,092.315174 B / 60369 WUbc1qw5u8hmq8hr…gkcue 0.13076021
081623f751…21bfee081623f751032c6b46d2…2015-08-3116:36:04604430height 372398in+0.00010000in 0.00010000 / out 0.000000000.000700006,073.06073 B / 24292 WU1Hd67ytgWJGR2T…LG23B 0.99120000
86ef8f96bb…3c0b7486ef8f96bb894c3ddce6…2012-11-0819:32:32769744height 207084in+0.10166644in 0.10166644 / out 0.000000000.001500002,334.02334 B / 9336 WU1NEU779yvLaFk3…CbzqL 50.00000000
fc2ee39c04…9759c4fc2ee39c044198cd963d…2012-11-0617:04:04770080height 206748in+0.10042317in 0.10042317 / out 0.000000000.002000003,036.03036 B / 12144 WU1EDYvssYAET4xe…pvTBx 2.739993581Q3nwtzFMfBqL1…aLrMv 4.998773121NEU779yvLaFk3…CbzqL 50.00000000
798771c16d…3d1421798771c16d354c7b9790…2012-11-0408:16:03770428height 206400in+0.10279400in 0.10279400 / out 0.000000000.000000002,890.02890 B / 11560 WU1NEU779yvLaFk3…CbzqL 50.00000000
eb434dc825…8b15deeb434dc825bee894cfee…2012-11-0123:40:59770776height 206052in+0.10198005in 0.10198005 / out 0.000000000.000000002,028.02028 B / 8112 WU1NEU779yvLaFk3…CbzqL 50.00000000
43cfa95467…127c0143cfa95467c3444f7324…2012-10-2815:37:48771410height 205418in+0.10467224in 0.10467224 / out 0.000000000.001500002,401.02401 B / 9604 WU1JojoabNWerWFu…KBAgF 35.72727404
bdb2967e7e…51ea1ebdb2967e7e01f7c46c77…2012-10-2610:31:43771795height 205033in+0.10229240in 0.10229240 / out 0.000000000.000000004,796.04796 B / 19184 WU1NEU779yvLaFk3…CbzqL 50.06750000
7f55401c0c…959a9b7f55401c0cc131b52184…2012-10-2404:32:31772131height 204697in+0.10149315in 0.10149315 / out 0.000000000.000000002,437.02437 B / 9748 WU1NEU779yvLaFk3…CbzqL 50.00000000
da652bfdbe…13e827da652bfdbe97b3a9e2f1…2012-10-2209:10:39772393height 204435in+0.10341644in 0.10341644 / out 0.000000000.001500002,470.02470 B / 9880 WU19rsPoAjFCe3yH…QGAfE 46.08822417
80a948b4fc…1ac76880a948b4fcd277715be1…2012-10-2003:09:22772752height 204076in+0.10411879in 0.10411879 / out 0.000000000.002000003,083.03083 B / 12332 WU1NEU779yvLaFk3…CbzqL 50.00000000
865e819e8d…20517c865e819e8d8542b47fe2…2012-10-1801:12:29773060height 203768in+0.10303910in 0.10303910 / out 0.000000000.002000003,285.03285 B / 13140 WU1NEU779yvLaFk3…CbzqL 50.00000000
260d91b675…208a26260d91b675716afa9e19…2012-10-1505:42:39773479height 203349in+0.10267043in 0.10267043 / out 0.000000000.000000004,874.04874 B / 19496 WU1KRoGVd6yPe3cb…RvJJj 21.388709191KBf1hg1JNpwEF…SSV4R 19.506119291NEU779yvLaFk3…CbzqL 50.00000000
e0a46011de…505785e0a46011ded8802b64c5…2012-10-1301:25:02773798height 203030in+0.10173291in 0.10173291 / out 0.000000000.000000002,857.02857 B / 11428 WU1GJ1s6cSDiurH9…nR8z1 27.350674781NEU779yvLaFk3…CbzqL 50.00000000
2be29b40ba…e45bbd2be29b40ba6d6ccf22f0…2012-10-0919:06:58774272height 202556in+0.10247136in 0.10247136 / out 0.000000000.003000005,372.05372 B / 21488 WU1Hj33D665XTQnq…85P3r 49.489346791NEU779yvLaFk3…CbzqL 50.00000000
8a6ca35649…6785688a6ca3564988319ad4f9…2012-10-0704:32:24774663height 202165in+0.10508955in 0.10508955 / out 0.000000000.002000003,468.03468 B / 13872 WU14pifTh2EEPaXM…AjiPA 19.021969061NEU779yvLaFk3…CbzqL 50.00000000
315d5a0602…61cb11315d5a060231964d7ca8…2012-10-0501:00:58774972height 201856in+0.10134853in 0.10134853 / out 0.000000000.000000003,117.03117 B / 12468 WU1NEU779yvLaFk3…CbzqL 50.00000000
bb3f7b958b…3ace8cbb3f7b958b26f329812f…2012-10-0315:48:31775152height 201676in+0.10549375in 0.10549375 / out 0.000000000.001500002,300.02300 B / 9200 WU1KKreB9EhzMJ4s…5AAMc 49.61796334
b49f6aab76…254fdbb49f6aab76fc69effd69…2012-09-3010:35:28775611height 201217in+0.10063208in 0.10063208 / out 0.000000000.000000003,004.03004 B / 12016 WU1N58vZG23CSw8f…dXcFB 3.123971881NEU779yvLaFk3…CbzqL 50.095249611NdaxhxqBuK1gR…Lzuve 3.34346550
2cd1ea19eb…1012f72cd1ea19eb0b7e9bc6cf…2012-09-2901:29:31775837height 200991in+0.10199741in 0.10199741 / out 0.000000000.001500002,673.02673 B / 10692 WU1QbtQNemqTpFwH…2yUoa 45.06891983
efdda14c44…90189aefdda14c44a5a9762bca…2012-09-2703:04:43776144height 200684in+0.10151992in 0.10151992 / out 0.000000000.000000003,162.03162 B / 12648 WU1AMe1GrjdayXwt…vjPkF 2.207566721NEU779yvLaFk3…CbzqL 50.00000000
8aaa33a8ec…9969fd8aaa33a8ece87993e3ac…2012-09-2423:07:14776446height 200382in+0.10203148in 0.10203148 / out 0.000000000.001500002,550.02550 B / 10200 WU1Bgku1kwZmk5Ci…mdBXS 1.310216741NEU779yvLaFk3…CbzqL 50.00000000
4e15b06509…0740f04e15b065094719846d2c…2012-09-2221:01:38776766height 200062in+0.10008202in 0.10008202 / out 0.000000000.000000003,367.03367 B / 13468 WU1HAmft5RWxSqPq…4o7ur 44.269755761NEU779yvLaFk3…CbzqL 50.00000000
Explorer: https://blockstream.info/api · same third-party caveat as above.

Live balance — queried by your browser, right now

This block is filled in by JavaScript running in your browser, contacting public explorers directly. Nothing here comes from this server, which is why it can succeed even when the server has no internet — and why the balance may differ from the one above if a block arrived in between.

Querying block explorers…
P2PKH · mainnet · this address
…
P2SH-P2WPKH · mainnet
…
P2PKH · testnet
…
P2SH-P2WPKH · testnet
…
Total across these addresses—
How it works

What this page does — and where each answer comes from

There are two fundamentally different kinds of question you can ask about an address, and this page keeps them apart on purpose:

QuestionAnswered byNeeds the internet?
Is this string a valid address?Pure arithmetic on this serverNo
Which address type is it, and what script does it stand for?Pure arithmetic on this serverNo
What other addresses share its key?Pure arithmetic on this serverNo
What is its balance and transaction history?A public block explorerYes

The first three are facts derived from the string itself and can never be wrong. The fourth is a claim by a third party, and the page says which explorer made it. If there is no network, the first three still work perfectly and the fourth says so.

1. What a Bitcoin address actually is

An address is not a key, not an account, and not a wallet. It is a short, checksummed encoding of a spending condition — technically, a commitment to a script that a future transaction must satisfy. The blockchain never stores addresses at all: it stores outputs locked by a script, and an address is simply a human-friendly way to write down certain scripts.

That distinction explains most of what confuses people:

2. The two encoding families

Bitcoin has exactly two ways of writing an address down, and telling them apart is the first thing this page does:

Base58CheckBech32 / Bech32m
Looks like1…, 3…bc1q…, bc1p…
Alphabet58 characters — 0, O, I and l removed32 characters qpzry9x8gf2tvdw0s3jn54khce6mua7l
Version byteOne byte prefix (0x00, 0x05, …)Human-readable part (bc) plus a 5-bit witness version
Checksum4 bytes of SHA256(SHA256(payload))A 6-character BCH code over the whole string
DetectsAny single-character error with overwhelming probabilityAny 4 errors; published guarantees for longer runs
CaseCase-sensitiveAll-lower or all-upper; mixed case is invalid by design
IntroducedOriginal client, 2009BIP173, 2017 (SegWit)

The Base58 alphabet excludes 0, O, I and l precisely because they are the characters humans confuse when copying from paper. Bech32 goes further: banning mixed case turns a whole class of transcription error into a hard failure.

3. The address types, and what each one commits to

This is the part that makes some addresses convertible into others and some not. Every address commits to a single 20-byte or 32-byte value, but what that value is depends on the type:

TypePrefixCommits toscriptPubKeySize
P2PKH1…hash160(pubkey)OP_DUP OP_HASH160 <20B> OP_EQUALVERIFY OP_CHECKSIG25 B
P2SH3…hash160(redeemScript)OP_HASH160 <20B> OP_EQUAL23 B
P2WPKHbc1q… (20 B)hash160(pubkey)OP_0 <20B>22 B
P2WSHbc1q… (32 B)SHA256(witnessScript)OP_0 <32B>34 B
P2TRbc1p…x coordinate of the tweaked output keyOP_1 <32B>34 B
Why this page sometimes refuses to go further

A 3… address tells you the hash of a script and nothing else — it might be nested SegWit, a multisig, or a timelock. A bc1q… address with a 32-byte program tells you a script's hash. A bc1p… address tells you a point. None of those can be turned into "the other addresses for the same key", because the key's hash is not in them. Only P2PKH and P2WPKH carry hash160(pubkey) and can therefore be converted into each other.

4. Sibling addresses: one key, several addresses

Because P2PKH, P2WPKH and P2SH-P2WPKH all commit to the same 20 bytes — the hash of the compressed public key — any one of them determines the other two. This is not a security weakness; it is simply the same commitment written in different scripts.

It matters enormously in practice. The classic disaster is a key whose coins sit at the P2PKH address while the wallet in use only ever looks at the P2WPKH address (or the reverse, or testnet vs mainnet). The wallet reports a zero balance and the owner concludes the funds are gone. The coins are usually still there, and looking at the sibling addresses is how you find them.

AddressTypeSame key?
1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMHP2PKH mainnetYes
3JvL6Ymt8MVWiCNHC7oWU6nLeHNJKLZGLNP2SH-P2WPKH mainnetYes
bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4P2WPKH mainnetYes
mrCDrCybB6J1vRfbwM5hemdJz73FwDBC8rP2PKH testnetYes
2NAUYAHhujozruyzpsFRP63mbrdaU5wnEpNP2SH-P2WPKH testnetYes
tb1qw508d6qejxtdg4y5r3zarvary0c5xw7kxpjzsxP2WPKH testnetYes

All six rows above are the same private key. Two of them are on testnet, which is a different network entirely — coins cannot be moved between them, but the same key controls both.

Siblings are a strong hint, not a proof

Deriving siblings tells you which addresses that key would produce. It does not prove that a particular sibling address was ever used, and it does not tell you who controls the key. Watch how the balances differ across the family — an empty mainnet address next to a funded testnet one is completely normal.

5. What validation does — and does not — mean

This page verifies the checksum, the character set, the length, the version byte or witness version, the program length, the case rule and the padding rule. Passing all of that means one thing only: the string is a well-formed address that no Bitcoin node would reject as malformed.

It does not mean:

6. Reading a balance correctly

There is no "balance" field in Bitcoin. What exists is a set of unspent outputs, each locked to a script. An address's balance is computed by summing the unspent outputs that pay it:

balance = Σ(unspent outputs paying this address) = total received − total spent

Three consequences follow, and the page shows the ingredients separately so you can check them:

7. Reading the transaction list

The history this page shows is written from the address's point of view. For each transaction it computes how much the address received, how much it spent, and the net effect:

DirectionMeaning
inOutputs pay this address; no input spends from it.
outInputs spend from this address; nothing comes back to it.
self / netBoth sides involve this address — a consolidation, a change output, or a self-transfer.

Other columns deserve a note:

Why the list may be shorter than the transaction count

Esplora-compatible explorers return at most the 50 most recent transactions per address in one call. This page asks for fewer than that and states the total transaction count separately, so a busy address shows something like "25 of 172 transactions". Paging through years of history is what a full explorer website is for; the links at the bottom of this page go there.

8. Privacy: who learns that you looked

Validation happens entirely on this server. On-chain lookups do not, and there are two separate paths:

Server-side lookups (the summary and the table)

This server makes the request. Your browser's IP is never exposed to the explorer — but this server, and the explorer, both learn which address you were interested in.

Browser-side lookups (the live balance block)

The JavaScript below runs in your browser and contacts the explorer directly, so your IP is visible to that explorer, but this server never sees the query. Turning the on-chain option off disables the first path entirely.

Either way, an address query is a privacy leak: asking about an address links you to it. Reusing one address for every payment publishes your whole financial history to anyone who looks, and asking a public API about your own addresses tells that API's operator what you hold. If that matters to you, run your own node and query it locally.

9. Special and unspendable addresses

Some addresses are famous enough to be worth recognising, and this page labels them:

AddressWhat it is
1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNaThe genesis coinbase output — the first 50 BTC, never spent.
1BitcoinEaterAddressDontSendf59kuEA deliberate burn address whose key nobody has.
1111111111111111111114oLvT2The all-zero hash160. Unspendable in practice: spending it needs a public key hashing to twenty zero bytes.

Burning coins is a real technique — it is how some protocols make a commitment that can never be redeemed. It is also, obviously, irreversible.

10. Quick reference

ItemValue
Mainnet P2PKH / P2SH prefixes0x00 → 1… / 0x05 → 3…
Testnet P2PKH / P2SH prefixes0x6F → m…/n… / 0xC4 → 2…
bech32 hrpsbc mainnet, tb testnet, bcrt regtest
Witness program sizes2–40 bytes; v0 must be exactly 20 (P2WPKH) or 32 (P2WSH)
Checksum constant1 for v0 (bech32), 0x2bc830a3 for v1+ (bech32m)
Address length limit90 characters for bech32, ~34–35 for Base58 mainnet
Sibling-derivable typesP2PKH and P2WPKH only (they carry hash160(pubkey))
Explorer transaction limit50 most recent per address, per request