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-17T16:20:08.487Z
manifest sha256c64f0e31120b23b2ef7bcd4907884965a5fa1e633a99cbb10f6ce2eb186df01a
screenshot sha2567e7c00d806858ab685ff2260269acde8ebb33afb4795486ebd6de2a75fb99bf1
html sha256443eef0b1af1de73ed440c2570cf912c16e0736dc5d80d5cd996fc9ce76a51fa
proof⛓ timestamped on-chain
txidfbfdac7587236004bafdf2b0aae9d4334bd66e11a3698f2f4b6946db2508e7c1
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,735 · 12,034 confirmations
SPV proof & how to re-verify it yourself
block height962735
block merkle rootf8e3ad60021acd06784747311faacb2433e124411d06e60380c5e7ce889ab7be
tx index584
branch (12)7e429a0bf1f8142fb143ac596b9edfe460830077626af61da0bb2782635237d8 869b6bcc686b410697fc9d91d59ae3ea7ccc6048e6b8a97e08c175ecf2f1ab14 87cee402b641dd5acb8afed6d861d88032038dd8f058c5fba69ff59220c7497f 04f7302658f20a2f433992bb659601f885bdbfedc037b6bfd8af14f7447adfe5 b4b38a1c530c263abca3fdb12ba9f2e696e227bd5ec6d3b5267beed3186758f2 e98262ce4ef1ff83f47f57e42ce0bc69c89fecd0685d7cdbfa2bf4a48999d06d 592ff2e0462b309ca30832ab36b5aea065e36b3e7ffa0b5bdae411216112efe2 618b1b5bc33e7f39807efe2932f7466d6edc34411e43a6fce8eea63a0d4f2520 cee579665a014a1932eaac6a16ca232f25594a5a8551f4bcb08b5f05b7f085c7 e4fca5e1f2cdc36b6e99cb2c4c508a88e980edd62b5ee68379cbfccb36b1943e bdb184ea65afcab5d9c6a6369ca1e583b203c5fdbbb2f7dba4ce87fe7e161d30 11283c1171478061e7274267176cdc9a538d461ebcd3f682fd198f8f04ece11c

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