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-21T12:20:06.340Z
manifest sha256317665c671ce6112bf39138c6615d45231d428f4f7543d4e58769d26a2b91e58
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid7b48a118c71e1be8f8f2a0995e1104474b519fb53f1de0ed22a10cccb45ad448
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,291 · 11,478 confirmations
SPV proof & how to re-verify it yourself
block height963291
block merkle rootbcdbb5e2c4db28f19b7334d72aae3a175cd6a82d0d5019b9e72150ddf595cc05
tx index24
branch (7)5788eab403557c39c3423293fdd175f3021c17e23bfad83815b03721fa8aa621 9e60efa0cd3975d8c04818060ab8b3f84c83c6413cd32fbf1920d83d404a5108 ec24206d5369c2816246559a1402bc31f1208c5417b3efb1acc235c54f708355 bf9e02808ce622ecc5dcccf758677694dedf975f9cb945d1c022ec77e85178a0 d376a2f40d4f0120f108564fe716223062006697d9cc9dc2bd04353cd1dd8161 f194b1151e58c9a928c6c0c61fdcab0f1c54e5e424074aba63eaa592de191582 f0d4a90eeac889e74620eb3f193693ce4cd9dc4ec563cef829cf17869300e519

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 963291 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 317665c671ce6112bf39138c6615d45231d428f4f7543d4e58769d26a2b91e58; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 317665c671ce6112bf39138c6615d45231d428f4f7543d4e58769d26a2b91e58, 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