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
captured2026-09-05T16:20:08.946Z
manifest sha256250d217d38c2d037b5f348fa9215fda6b0d56f631f331fc08da97e902d326795
html sha2562bd67d7b5ff03d99392e70125d10293a2e82ff5d7e3a6477b8e4b280dc618daf
proof⛓ timestamped on-chain
txidfea071613538abc473d9384ad76559a40f35fd75cb12db019965e209678f9c39
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,451 · 9,318 confirmations
SPV proof & how to re-verify it yourself
block height965451
block merkle rootfcfee6da1a55d0d4fdd7f1ed52baff1cf69b85596cad996e6223ff4465d036c3
tx index2273
branch (12)824c2a163ad13bde428292cbc9699d45d21c66963031f75edd1bb3ddafe791cc 736595aa5e3ca55beec8f188045ed45f5891a564a0eab154d210adf969a4c3a4 018e986f72b0a24961d84593c727568fd4142b2f3c6d0ed376b80bb5722af754 3cb220eda086843def0736341a5024586b2cd69ecc28b05d2a68f961c835cc0c a1f03dcba42d6624f542c53204b34719161030b30ecc9cf59650650a072e5076 0eeaed90af556703277ec57dc86ca77ba15a1833356f1f58116e14d3ae1c2ea4 434f1e00ab5b3e795941a7ba8fc862268fd83647f591e7cdee55182eb4af3a19 939c87cd941c6fb208e6c7c857665f605d8cb0b8bc6a59c251057e518522b164 1b9520b6ff5b31169b200cbf067edf402c8f4b782fbd38bc16f026e0cf58c8e1 4a061f55cbe41cb80b27e41afa7729b93089653c75f6975d097c1255e0fff09b 1767ec421e4b6596380b27b6f279032802bc1b7aceaa2577174fc7f0d2d45cd7 5822fd44abdf0ba9c033398f039c9a849c42b80f65461d807bae1025ccecbf6e

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 965451 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 250d217d38c2d037b5f348fa9215fda6b0d56f631f331fc08da97e902d326795; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 250d217d38c2d037b5f348fa9215fda6b0d56f631f331fc08da97e902d326795, 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