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-26T16:20:08.863Z
manifest sha2569d232268752d4fb3fb87d74f99ba8b9b5474a9420786361322f7bfc312765de4
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txidcda46a23b17602ca968abe39e663ed93c9c61a05c3c650176556fe5ba7a85e8f
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,021 · 10,748 confirmations
SPV proof & how to re-verify it yourself
block height964021
block merkle roota67873dbe699b80091ee28c4b17f304456b053c1778f2bdc2367b5f7f1eb3e82
tx index17
branch (8)dc33545402aae70e575e0abfc216020db46bc330fa74a8b74f35a6391f950c31 9da80daf5baadc834e92e1e321320e64fa03bc90c0a601e56af6425ae3df3049 0ad75c562b9eeecd21e0814028acdd34bcf130a7a77ed5bc7adad9fb37ccc3d7 c3d900fc318a653320ccf9c5e5ad99049a4102768cfd6c0bc50c239d2ecefd4d e81a93bf63f8a0791935a23cea2122ff76a86f5ae365fead7204d68bb2153f33 12fb9f2bd5d8d56b9aefac2f35ce24fea1de2aee7a551638af8185b5edc6b10a 418654a3f61f23cab18f061454f056810154898aa6026791260870760529e6af 90ba7b8ce0f43c68cbd610b555a2cb9ae332c181a8b1bd776f8f00c9253ce4e0

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