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-10-29T16:20:12.379Z
manifest sha256ed68c4ffea3b3cda6d4e4d74be69ccec407dd8abd41f8597c23129757519abd6
html sha256b10853da0a25cabd48b86824e05ca033d568b082309abdc1444366f809d21708
proof⛓ timestamped on-chain
txid9f4284ee90b980ca4503da92c0c89f7bae18ab5589d19067598a565b3c3501da
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 973,211 · 1,558 confirmations
SPV proof & how to re-verify it yourself
block height973211
block merkle root741ac2625632fb3ace08a0b194b65ef5887b43b354610df00fb151276d20e22f
tx index455
branch (10)ea0e859d97e11429ef91ac02ef85fe17c5855eb3a63b4745f88546b2eaa66148 b32290c42a5260678109c4ade2ce0eb2187c4cd0bed2010cc1af33dfabf06789 2da6546133b38a4a2e28bb5298cdb83b30d3b68e44e432b8282e4137a84d7858 fb650583c1bdc9c612a341e67488210fa3b4ed6fc1360ba44021050ff20798a3 8a54a4ff60e872dbe7ba916cedaf339f95c783f2dba2d4143e54b8e43e7082b5 c074685358fd2a1cbfa6f4a091f5b0568a1bfe823251d947c1f49e6b6f16b8a1 5c69a297da8e82338d0e5f135d9d87b40993aae3100527c1005e0bafe8a6a4b5 91567b9a099c5cdbc321a231ff03f537e088f2e5da75d16d23d6868926f81335 d5479e34f6a16a04960f0842a61f9be049697b3e34de3e9aa220d47e3bb931e0 cef0fd0dda33816711735548b8ec7ee06673b6b4ed7f743bc18af363312df55a

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 973211 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 ed68c4ffea3b3cda6d4e4d74be69ccec407dd8abd41f8597c23129757519abd6; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / ed68c4ffea3b3cda6d4e4d74be69ccec407dd8abd41f8597c23129757519abd6, 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