Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — 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-23T20:20:08.679Z
manifest sha256741cbdc4f966cd36763bf9eedd3233d80162ff624ab1e0bd30a74f786124063d
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txidf8345ba90d1cc4619982e7d280da4c8b2b335e13affe7602025eac7197015770
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,610 · 11,159 confirmations
SPV proof & how to re-verify it yourself
block height963610
block merkle root215a199bc2b58e549df3222f20c846cdd5b4d0680daa08596eed9371041137be
tx index1680
branch (12)3481fb497033c986419face138d25fa4cd3da22c1509f5454dfcac55c4ee9704 69311281c13cb4cd55db48e6bda15748f836894a7d5efafa3d6412726d6034d6 4c4227ae2fef2bd8528ad89095e5ef4a8282fb9bc1ee3484dd6dcc20457dfd3d 84fa3c45070f7e2a3e30ab706fdcfc6ec7ede832caa4c9fa41c52008504667a0 c4508b8b0641747e43dcfff2ada04bbccd7e7a4fb70772b7020c3e98985c5372 69c9259064d7e2d6ff93a7254e120c9511a73b35a5fd09cbd396a72dfbaf7014 ac64a361ea150bdb9f42588de4fab81f9848ec4b3af4ba4f5069e90a2354bdf5 068a8f6b47075a73474c029c0d1f36cf3ce775f5f76feeffc60075665a28eae5 3968acb22b6ed806f1d134b95c3536da66fe9e3b191f6fe2685d057cbd415b53 aa20df0bcb417486c202cc3c99f7eadb4c3a11cfc725801cc18b44452180302e caa160430d58ee97a1550d858d94e74c5bfd891f1cea651f151095cfb2fa053b 1bd17afefd1e7e8aa7eef8a189f3a57596add4efdb2c910f532a7cac88b25e03

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

Other captures of this URL (179)

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