Web-page notarized

A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one

Rendered page — archived HTML, sandboxed · click to collapse

Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen

off by default; remembered for future views

page snapshot

captured2026-08-19T04:20:05.062Z
manifest sha2566919deb5a9a153adbf484dd7973cb2f04a088246ed8e523ed3a359e361d0a1b7
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha256eb81f4a853f44042c661e01024febc475c0114cbba3994784f5599e164d28ef3
proof⛓ timestamped on-chain
txid0ed3638f20f98fb10735771cc7d14a31536598bacac1921dd58d1e31b8c7a236
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,944 · 11,825 confirmations
SPV proof & how to re-verify it yourself
block height962944
block merkle rootaddb131c218daabc9e9e29d9b169aa146d70776cfd022d66d8120d0ec7b985f4
tx index547
branch (11)a9eb916db1279e615f00b7c824c8509d2e39d5ac86b1e3e761fe932ea3478dea fbf07155a7f5bbd249f887c4bc9245606f14372a98d68d000f6b1c421cb47438 4f71c3ec242289dd4a4fef44b3d53b103d1dbd1f3197da40c671b5a06caecde9 8c6ec1da489305931a3feed8aabef933545267c2689b67486075b5824401c80e 30e9a2e6d7d17477565979678976e4340af63dda171e5e2e12cbc15be5ffdbef 7c23ec4a0ad000bacafc9b92180865c83832c90d25d2e8eaee10d4b1aafe7e96 45763668472e3aa47ecd1a0c4efde3e2db16626ceeb9705afbd80fdaa7d5feb3 5c26d4c4259029b9604941319d1fd95cc91d399f6806fb3d1f03a1ce711e27ef b19fdd611121f66c8b22eed446bf5e9ab4edafd6640fb32d2c848527ac545d03 d12f74df5b0f15c8281118129cc9369675c91000899cb599c601b59efcd393f2 325485f9543bbd1533ddade560c5c7aa21ca4efd3f892fe0325153b6bd348258

Trust no one: double-SHA256 the txid up this branch — at each level your hash goes left when index is even, right when odd, halving the index each step — to get the block Merkle root, then confirm that root is the header at height 962944 on any block-header source you trust. We verified it against headers we run ourselves; you verify against yours — no explorer, and no bsv.cx, in the trust path.

Prefer to check it against a second independent source? Paste these fields into our public verifier (POST /spv/verify) — it folds the root itself and checks it against headers we sync, so it can only ever make a bad proof fail.

Or take it to your own tools in the ecosystem standard format: BEEF (BRC-62, tx + proof) · BUMP (BRC-74, path only). Any @bsv/sdk client verifies these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).

keep your copybsv.cx stores this snapshot as a convenience and does not guarantee to host it forever. Download your own copy now — with it you can prove this timestamp yourself, indefinitely, without depending on us.

⬇ screenshot (PNG) · page HTML · manifest JSON

Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.

Verify it yourself: the manifest is the exact JSON whose SHA-256 is 6919deb5a9a153adbf484dd7973cb2f04a088246ed8e523ed3a359e361d0a1b7; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 6919deb5a9a153adbf484dd7973cb2f04a088246ed8e523ed3a359e361d0a1b7, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (185)

← back to bsv.cx · JSON · saved HTML · ⚠ Report