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-26T08:20:08.551Z
manifest sha256989204b3ae4e795987542ea08576a2b996a8411e23eaaae9ac80939dbf41a0d0
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txidc743299b705938b9e1e61abb873477f208780e836fbc95e84208f09440023b55
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,969 · 10,800 confirmations
SPV proof & how to re-verify it yourself
block height963969
block merkle rootb103e7a574e89706029c3886ec79194d4044fe79210f9ee50fcf4b590db2f5eb
tx index616
branch (10)cfebb86e1e64d14b7521bd974d41281f4d0702bf16331eee6dcce3d9d8fa60f4 5f3a41acfa812bc09f2ad22fd398ec149f0a0675f8e21f98d820bb453d32149d d02e7c8ae775ef0ab419b31e6e438886d134391ed0e01ba4a9635f5eb42dc30e 5143baf61e291cc0423aa1e24e1d80c4d3ffda20e6adc783546fb215eff8a2eb f1512a6140f9a22ff9bd3ca3dc16fd241715b0ae6a6cf903cf827d7fdaa04ab5 77a41f1a5b91197824ff8432faab472d74bd1790b16763a0b5e739e452b64dd4 8529c4b40dd6091d100b48c3c3b754b7355c7ea9ab717b700c0c285edb75c043 5a942514c3e0eeb938438710ffab5c8b345d3d5054960d7b1300ae814f35dbc8 8850d5494810d01e0e76e704d55e77dd701f9c6e2047e7fbf63fd72a3c336bd0 e8f2522680cbd5cf8825dc81c8aa1ee1fd35cbadae33d583cdf1ee86e6e915fb

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