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-15T08:20:08.267Z
manifest sha256291843f8f4c05830de1181b5e487fb7756c5f1c73d93fb1432df26192f307cec
screenshot sha2567e7c00d806858ab685ff2260269acde8ebb33afb4795486ebd6de2a75fb99bf1
html sha256443eef0b1af1de73ed440c2570cf912c16e0736dc5d80d5cd996fc9ce76a51fa
proof⛓ timestamped on-chain
txid2974759352353ea6138daab9fba8defe16204ba3b1dbb6fdd7bf4b14072c3e24
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,402 · 12,367 confirmations
SPV proof & how to re-verify it yourself
block height962402
block merkle rootd1c1dc56463e09365c03d94e53344e6182ddf79f972688e301788dc07e954f7f
tx index44
branch (8)cf766f6fac992fd1416fcf6d5faf7a320bcccbfbd5bd01686a6f72407547c33c 001bcc3eb5d6e6aac1f7826b1ddb486e29bcb0ccbaf97271ad51f53fdacf26af f8cab4609e8bdcd7c9fcc7a9a0eb4ebac18cbfe57c5f49697b372de99af9a4f5 548fd3d754e06d7610efb51c3e63ed641629b0185f984cf92cd6f75d83e7bf9b 94678f1e2a0564301cf590b5706e0ecf3036bcf22ace53331966e3b2a35e4f0a 47e232b3632d1f6744a4a66d183285fe3c1e6e3fd24f2029a0cf8d0c80e1d4dc 0a5600449ffeaa01ed0c985853b2ee74d42b805f8559f093a47d7e7b2c88994d aefe4f46fb8934414ff2802b0a8ed4e576f519f685a417f66f9bab0ed5692c84

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