Web-page notarized

A tamper-evident timestamp of a page's content. Pay-per-call — 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
captured2026-11-05T04:20:12.805Z
manifest sha256347aa3b2c7169b2b56f4488194dfc94917ad748efea4ec863ad489f54dac9a1b
html sha256968fe62bfcf5f3236ea001e8297df8e3406d05c04facd9796d2d32585e75fc82
proof⛓ timestamped on-chain
txid4a763a586f06074de976431a9df5b7059c0805830a4fde9796527aa544203b6f
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 974,138 · 631 confirmations
SPV proof & how to re-verify it yourself
block height974138
block merkle root38b85faf16a6a891637b56747d6ff2e3469d1930e6ae0b4b1a903e5de2d6cf4c
tx index786
branch (11)fd4d713cbfe56d875f8796d7288dd4e1ec65a09ff87acf3ff362b52345e3e1a5 f95b8bc86d6417e4bf85f84240cf44816d2e84e17d3d1afe5e767bb1dc3be591 5ce50fd1e3bf21fb602aefcf78d68dbd9b96a6a739945650c1ed315441d8cebb 9a89c0a3a7599c49065efdc4b60ec10be3fcba2a7f23d4c85278a5ba0541a8b1 2dc74f594730cf1960d859482b9e169fa880e69fe04f1394875ec2a9bec63018 7de12ae7e087d7696f6fa457c7da2e76b3e295246083764024136b870aafcb52 d3ae7761a2cb4a9b31608ce050b1f0977f95abdf255c6d98b324c0c52c589ff1 4be0550575f623dceaec5ef8ddfd8fe747490f9e88d16672c5cb42427e06bd8f 2e69847a0469d1375ee826a68275b80ab9c0e73aa83d570e8834471d3bffbd15 5c745f2306fe45d3698f9859716bbc50e577f5c60dbc3653cb5829b82391f112 5ac3ca5f904a64b27bdc9ac668f00f9c70b83f25febf1b4f48b24caafb902e02

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 974138 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.

⬇ page HTML · manifest JSON

Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — 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 347aa3b2c7169b2b56f4488194dfc94917ad748efea4ec863ad489f54dac9a1b; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 347aa3b2c7169b2b56f4488194dfc94917ad748efea4ec863ad489f54dac9a1b, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (600)

← back to bsv.cx · JSON · saved HTML · ⚠ Report