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-23T04:20:05.443Z
manifest sha256b23cdbb53381c1ebf30130d766cbb15f0cf89c9bffc85f4460659b66fd4f9678
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txidb4d2ab09ae5c7c9c46cf2f055e60547c9ef9691d0b06547599e03a5e0945e802
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,507 · 11,262 confirmations
SPV proof & how to re-verify it yourself
block height963507
block merkle root1c9cbb28a434a73fd85dafb2a809756ea05033ba8849be2a2c0375f999c55b25
tx index384
branch (10)9c949c873a63cc8511312c07cc7528a109cf786712b2c057dd3217e4bba53d6a cc335d3521ba2844742d748b88c85000ae64309f1d3d7c8f7d567e093b2bcd06 b0c726fe4d91da578dcaf53166aeda8be6487edba0af7a00eab2716f2509cbda c77b5bcedf3089db0d34ab519641387c1080b3dbbccc1afff5b66ec59f435d34 0bdedd544c81221a1ee0469175e52355c7a80eddc7cf53ee9228c8cf9ca47a05 3dd10974dcf5c0c4a3f5b60b7794867f1a98ae3a2eb6e80d00749eb2540fd919 40ed019dc40e96f826ab3a72e74fdf263bda765900c4d57c3a0897451487bde5 7e2f327c3b205b524f8994a4133c1e2a97498a8720f23fc35fa2ea9965677855 4d06ab78172bba4ce1852e7e65c1ee63f3f22eb2dd2c3bab99b21d84a59f5869 92d8d8d71b213d8d856d7c67bdcdf4405d43e135aff12f200f4c7ab94ff3af63

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