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-24T08:20:16.619Z
manifest sha25665edc5e9a66c39676cb1ae804cb58cef20b9b51212b3dfa7e226ef321e6391a8
screenshot sha2565bc6d0b5cbe65f663e4a417c0d753b2ea91f07ab7c5dbc01c802106886f3950c
html sha256e25a3cde3839c83ccc22f4b02de66904ad9f618ec3a97b96557ef6c00ac559da
proof⛓ timestamped on-chain
txid00b94c5e841a66a17f1f42b0e1b4cd1e5b6b1f04c9bb2b78c82383ce8f72c10b
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,680 · 11,089 confirmations
SPV proof & how to re-verify it yourself
block height963680
block merkle rootd2438bc6bb53885acb387fe511e710663cd55a03a52a550b2063e07505ce5b7f
tx index1478
branch (12)e622afe88df4d1e104dda56c46825e3a17deb6dd79bd107f90a973c6fb61d166 76bcceb01ea046104aef7874372d4fa6d15357db6c82984881db123b5411c86c dfecf8ce9ac1fa2bf26e962f52d76499938c71f6c573567efade1dbdc21d82c2 5d7e05e3007869cf98daa0485c68e358176ad17690b63d965020186f9a16c85d f2368dc771d3fa67ae2042cd513bfdf527f5627df938d1b24fb7514960e2b4cd 031a77c6f6497bef1b8d35af606fbbdff06f1e4862c2b28ab622e2de9c982c88 1ae6a50328a84a629368b5f0c525e4f3a23168a6b6f3b31ba546520a7b24c0af d0935dce9b6425872db415321343a47d3bcddc2d74ef6c667e8bdf12ee124e00 2b6f355f4e14958e5c51dd7b216c2006a21604d39afaab4f57272f46c8c2ce6e 0d4983cdbeb47386b51deac0b9208636af0de5e328d4cd50b8d006b0b07254f5 692ef12b29017ea688c3bb91ebfb1205fb92ae4b6e4ac7a04b8a98e4d98788f2 2791d33bf11c86865fd7042c03ef71137180c79c8d56d14f29abe9cd08a9f0a3

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