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-25T08:20:11.669Z
manifest sha2567a3c5c665d117cca9ccc104f3d51e809ba14eefe9467a42274567792913138e4
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txidb93d0ec0a7165737711c939fcd2129715e81349b9b17df9c440679784a6c8947
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,821 · 10,948 confirmations
SPV proof & how to re-verify it yourself
block height963821
block merkle root6d50eb9bd196a0fc42d9b0d8d3c2580a88a84af75491baa6d8b93988607a0e39
tx index36
branch (9)bb6cb2ff1e7c95c15b42222105bc38b90e89103f1eb513efc6c8042adabb65a9 6eca051bc700bd1e556ccb5666385af409ece4467ecc38d63f4cabd58e2e678e a7c10e091b9ac3ab3ef577990d9c8310ce87880d4f117e94f1062a39571ee899 680b66592ec0ddf6fab9f2153ed59f1cae1da42f7b2bb286b635ff5af895052c 4feed4f33ac84bf8da9df97c850105b0fb485ded2f98db2bb753a27d1e4ecf95 89cd8b6f62af5d0323b593c240416afdfcebd0942ef463a02e0bb7d1ab12c51d 64522bb904c772cdb7b10e6f42415d294a82b8525f64a40adaed62ab3ecacd8d da4c9afdb55b50f06e6be3994f2c78900003e9d7cc2564294085caecbb7cefe6 18438634eba2fbe82efadd4f6d30c63801bd4cfe2d7bc295aa667e745b3a58fe

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