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-25T16:20:14.028Z
manifest sha256f257300a91a02c0931321bb76f40e12b688179efbe3c45891662c3e57a64ec0d
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txid47303ef684126d5e0fce10b8f38bc78771efa0027ac06d10e2c11bd4159136dd
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,869 · 10,900 confirmations
SPV proof & how to re-verify it yourself
block height963869
block merkle root77a32daee9badfa8521ab4f02bd03e82b6126ff68ca3aabbdd95593d383d578a
tx index65
branch (9)d25454710459411be6522153499c7577f4187087497699c71da1c6672f5129f3 c42435c89224a0eb785ea81a7d6393f47ba2f18e388f8ce3672610ee342c1178 7a061e11a562568bbf865634b75df6170385e93d8984b5ca17e8c4edb8aff2c5 15f8ad42ba1d979a5f73bb14244e41d4c4bc6ca3e878ddf00520d8d992e8fefe 6ec0f14a89943adafff703f40f5b273ba1a4ef8017d9cb3ae27fef6bfb7c1061 5076880716345c02c89df277538f07813339499207b3d8c6239ee04c92c2e23e 65b120e24aead957286658cbe960b50286add14bfaca9c9db43d2a5937668451 8a3d8f65cf75a463d040ecd8bafd3b683adcde82924255f0a9fb60ef6bd74b58 48cc28106dee56a6c1449ce96e0755cdd997e6ed51ba8ccf17b913c70aa15b1a

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