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

page snapshot

captured2026-08-15T04:20:12.323Z
manifest sha25680c3589aebf9c0e11fcdae7740a913297fae1861576c0d131c13ecece1efce53
screenshot sha256af79a6ae3720bdefc0d49b78a008df398e9a788904b1799fde9b8453411d5328
html sha256bb2f2c84fb033e7ee273f0b916cd5fe08022b9c007396f894f2793937982608a
proof⛓ timestamped on-chain
txid7533e8416e7044907199d9987af6aaa43b6bc0f39216f4c1527e5bd98c0eebb6
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,383 · 12,386 confirmations
SPV proof & how to re-verify it yourself
block height962383
block merkle rootc66567399d16b979b9ce1d73e9a0f51f21e2265621f8fa0826ebe9ca81376e0d
tx index286
branch (9)ec2f62f9f12b4bb11ca664c8748a6f6d223fabdc0c576cfafd35bbb1070804d3 941bf87e0a104f9401847da90b54027e2cc39cf6121056044920de951bd4e12e 908169f2c28b3ff2d1af67214724a5727992893fb386efed9fcf158f458e4778 14e01c0f4a4fe65cb2e0de9597a46556db593e56f67583360f6f36511a52417b 40d629e48c4624777988561e9eb11299b2cde88922c0ec22dcd541296c6944c4 a8586e09a1d3855036c6ec6b948e4c3a5e8e669ba8edd764e44557f93575f5fd 3592dbb376ee6c3fa35ae0c88a32c8b5e7f4fc58187bd3c4a69cff72094bebfe f2ce37f2a07f818f0f282008f90631b0ab2b6b8611f2f55a96f61b9a1ef390c4 39500c49ab21677ad04209b69ab4ca3eb2d88241cd30cfce52a42c27b2ce3a1e

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