358.47940237 BTC
Genuine structure 4/100 AES-256-CBC Core 0.18.0 or later
The balance sits on addresses whose keys are inside this wallet file.
Tracks the live BTC/USD rate; the exact amount is locked the moment you place the order.
Pay in BTC. Automatic delivery to your e-mail.
Summary
Our assessment
This is a structural analysis of the file itself, not a guess. Every point below is reproducible from the bytes.
- keys_without_keymeta · +4 55 of 201 key records have no accompanying "keymeta" record, although this wallet carries records that only exist in Core 0.13 or newer. Core 0.13+ writes key metadata for every key it stores.
- spendable_balance 351.04942530 BTC of the balance is on addresses whose public keys ARE present in the wallet file, with encrypted private keys behind them. If the password can be cracked, those coins can be signed for.
- keys_on_curve All 201 key records hold public keys that are valid secp256k1 points — consistent with a wallet that a real Bitcoin Core produced.
- txid_ok All 391 transaction records re-hash to exactly the txid they are filed under — these transactions are real and were really seen by this wallet.
The file
- SHA-256
- c7f88196eddd428e1095887af68ea75e81aebeea02bf72912da23231637a80e9
- Size
- 765,952 bytes
- Original folder
- 358.47940237 BTC
- Berkeley DB
- Btree, 4096 B pages, 187 pages, 884 records
Wallet software
- Wallet era
- 0.18.0 or later
- Oldest keypool entry stamped by
- —
- Newest keypool entry stamped by
- —
- Last opened by
- 0.28.0
- Minimum client version
- —
- Encryption
- Encrypted private keys (mkey + ckey)
- Key derivation
- iterated SHA-512 (EVP_BytesToKey style), 129,704 iterations
- Keys in the file
- 201 private-key records, 0 keypool entries
How this is dated: Bitcoin Core rewrites the "version" record every time it opens a wallet, so that field only tells you who opened it last — all 307 files here say 0.28.0 for that reason. The reliable evidence is the client version stamped inside each keypool entry, which opening a wallet does not rewrite. The raw integer is shown in brackets because some early stamps are non-release builds.
Show the dating evidence
- keymeta records use metadata version 12, introduced in 0.18.
This is the work factor a password cracker has to pay per guess. Higher is slower to attack. Note that Bitcoin Core does not use PBKDF2 here — it is iterated SHA-512 in the EVP_BytesToKey style, which GPUs attack faster than the raw iteration count suggests.
On-chain activity
These addresses have not been checked against a block explorer yet, so no first/last activity is shown. The transaction records listed below were read straight out of the wallet file and verified cryptographically — they are real.
Transactions stored in the wallet (500)
These txids were read out of the file itself. The chain history below was queried separately.
Addresses
For every public key in the file we derived all four standard address types. Addresses shown in red have no key in the file.
| Addresses | Type | Balance | Has a key here? | Label in the wallet |
|---|---|---|---|---|
| 1Jkn9wg1WbJdASNBPtQqdmm7wtrcSiATbf | P2PKH (uncompressed) | 351.04942530 | Yes — spendable if the password is cracked ckey |
Show all 1,005 addresses
Why this price
Priced from the balance at 100 USD per BTC, then converted to BTC at the live market rate of 82,882 USD/BTC.
- Claimed by seller
- 358.47940237 BTC
- × 100 USD/BTC
- $35,847.94
- ÷ 82,882 USD/BTC
- 0.43251780 BTC
You are buying a file, not a balance. The price is a small fraction of the face value precisely because the password is unknown and may never be found.
What is guaranteed
- You receive the exact file whose SHA-256 is published above.
- The file is delivered automatically the moment payment confirms.
- Every on-chain figure on this page is reproducible by you with any public block explorer.
- The password is not included and we do not know it.
- We cannot guarantee the password is crackable.
- Once delivered, the sale is final — the file cannot be un-sent.
Pay in BTC. Automatic delivery to your e-mail.