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-14T00:20:12.363Z
manifest sha2562a08e88fa43618289a783dc9c085599721539410b5616cc50e992b3fe65a2cc7
html sha256c6080734f2275ea7d59f879888a0f9b75cea6f97de5a1a884d207898cf3d2047
proof⛓ timestamped on-chain
txiddb2b636bd103c3abca0a9b809cd49fcf38be967e513b0d9268fd05237c0b5424
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 970,959 · 3,810 confirmations
SPV proof & how to re-verify it yourself
block height970959
block merkle root762b67abe4ee5a8f772b1ca482705497fdbb523164578f74c73f6c714f1bf0a2
tx index6195
branch (13)e0010d71705fc4e51604dfa2bbeb912cac9a8b27a078c563e1b54328d6601bec dd0f2efad26ffba5eb690032ce5f83e954e1589fbbd3521a5f27ee17869fa4f5 0657585fc4a4e054123138b8a61d0aedf292f6f337bf231569d3fa011d15107f 0f2d652765d96f8b19a09c58f7adc2ae812be96ab64aece1f932399fe9fa2ab1 4daa19b33c9b1ffe20db52898d74c79673296ff405f1de0d6cda1340cce87b09 1727628e24ef4395fd982ec362e57a3195896dc0092886bf20ce1967946b259b d2d1661cef27c4f8fa205a3cad5bb2c4ad610dc021dda1612e043e2dea3e8ff3 7d188197f85241326adb4aee12324a00455f2121f7146fd97d71a4f16297c034 bb90286e6c3d36f2bcc9069cb29967255e2622442c879f6d5e15afc437c92a70 1b802190b5a9619b12e7c7a10dd65e3c598d466dee989684af9aef40daba08de * fb5a1fa0e023d73474ae36782ec50281f79e9d74f8d0fa71d70dc300df040129 9273e4c34485d3008d8a6ba59dba3e9ab0dee14b061a55bca7636c57d134ec5e

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