Web-page notarized

A tamper-evident timestamp of a page's content. Pay-per-call — bsv.cx

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-21T20:20:13.047Z
manifest sha25619e606a10b84d120bd14627bd8038e233a2d28c02ed2f967c223eced2ff6e538
screenshot sha2563dda7ae806ecb15098ef0a8cee1604312740f98f475582b635bc698f4fd29935
html sha2564b78d57adf69c35286bd4fa47ef914194e618ba73f1df2377e19a2299dc88f87
proof⛓ timestamped on-chain
txid6fdf8d7cfcd45f7f117636435d8fec739752b20c7dcc3b817b5334a699033500
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,355 · 11,414 confirmations
SPV proof & how to re-verify it yourself
block height963355
block merkle root1a856bc26d0f730216c0f3f83abe7c58703c29ad230914789d3c5584b59a09e8
tx index1249
branch (11)47774a96d2cd222a14054c8d1a9bb1ec624b517bae531cd3839b6b3c28f6f088 cd70a89449bedc5c9553ba217bb0152f702250aca59c1a0a493b443136db8b60 80bba669a320778f6ae60722f3f7eb6c4223ada5037b4a7d1125c406735fc191 2fd2be6a7ef6e073b5570c0fd5bb08265b7efbec0054e4e08e987512bd15dd8c f3d4b2ba33e4ac58b348fe4180a8c424b3ccf58e0b3a93b663d6f48622ede6b2 b4b8f81e54639f6da70f1206faf959fbc18f032824682ce492ad75bb1b5442e5 4e8675cc17a6fb982fa7c7062bd02819c9efd6e8f1d7dd468ca7693529712da4 c3a96f88e15870884d727b1acba2c9a8eeea0143ea656845d4b10e35be7a2880 e23acd0dcd58261f942628f1eac629480facf8a01d2d656aabbb1ca3a08a695f b07bacebfd1a9e6c4f98b14d6874b57af601a575a398572aaf982e9ba730853d 7033c3b4da0ed93bc1de67cabc6ea0e47bb8e4ec37c88389d4cc546683cde324

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 963355 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 19e606a10b84d120bd14627bd8038e233a2d28c02ed2f967c223eced2ff6e538; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 19e606a10b84d120bd14627bd8038e233a2d28c02ed2f967c223eced2ff6e538, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (600)

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