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
captured2026-11-04T20:20:12.030Z
manifest sha25674e37f6f1f5983b3df422494a775e657365a52d8062f19cf8606f7b95686c7cb
html sha256c5c8f2a2f5a1caf4184938e0cacbd664b32c3ec09ef67c8cfc31826c1755b7d5
proof⛓ timestamped on-chain
txid6da5691f0080cf9ea62616fa1a21e83df0afc69ca78baf27803246d33264dc6d
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 974,077 · 692 confirmations
SPV proof & how to re-verify it yourself
block height974077
block merkle roote0595b1323229175ec7427f5816651ee3822cfc36fe82770a4158e96c84813dd
tx index4689
branch (13)014e6dec8c826f1493f58cb199ada95fa14d458eaaeccfd05328e67094423170 24c33d761763c525802b27d56913fadc8fa6584ce2de746eb75857ab0087983c a25466cda6324b523056f87db9806092f6e16a4d2081e256ad4985e16cd190c6 2b32fd0715a7bd74de5502a56aecd38246cb28ea85a3c7da96011dc266cd0fb4 c18e362ad6e63bf66e770798b8f95320c8eff279805c01d8855e7e3753a7df8b c2e58ef1996b7131c863231c356a3ced27e55ed241e94c7d2eb9e703edbe170e 8c4f021c4fd0bf29b6ba770109131a2658f3466a52bc79f877f5fdae780a4c23 47ce6ff809be21e779826ac58e00947668e770040320967691137f3fd0670f18 1316b95679057669398468d13d9556afac0705c1fb633d6644e48bfdda66105d 5c93787ecded035ff9679d99c7dc2446c8d51d459a58e192e51f1738fdc9592c af55c6f3ebd7f3dbaa3cbd47f74e4000148ccba6399098d5aa34eeabec2f40ed fea18db2ab6a635f5900b18122d593cd40b7997803c01923aa108c92b725bf03 a0bbddfbe9dca27cbd3c1d4a8f81cb319f18c325f996d679f9ab82392d27f7e5

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 974077 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.

⬇ page HTML · manifest JSON

Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — 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 74e37f6f1f5983b3df422494a775e657365a52d8062f19cf8606f7b95686c7cb; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 74e37f6f1f5983b3df422494a775e657365a52d8062f19cf8606f7b95686c7cb, 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