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-09T08:20:11.356Z
manifest sha256d8669f14f2bc1178cc17d2761bfce3494ca51d5333fdb9b2a16bbcdd0e6e0a3d
html sha256a09d35877500a8aeb6c8e208810d2ccc223d3be866a41bd3fd9069197b6b54cd
proof⛓ timestamped on-chain
txidfcb44797785a8c0b90b454de73d00d0243f92aac9ebc43c489bed4767adb2bb1
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 974,734 · 35 confirmations
SPV proof & how to re-verify it yourself
block height974734
block merkle root7b426161d4c906cad874da0826e3dc3e7534eeb7bbacbffe41f9055834cb6bed
tx index998
branch (11)c494263883b68591342b9d9f14c48851fcdd3c80d420ae8f7269ff48793efe48 878f375c97af6bac52199a0a066d7689eef5fe30275b476ee01508c689e1cf25 8b2356bc241c012bc191e21fb83752ca2e3809b67de174fb8166568d76455685 6c7da56e393c9d368032186418b92c63250d9de94840780b6d124b0e80d87f0c 5d89de2e0ef8b9ae18e1b329b686617f6c3b80c06e431892c8ab62cb62afe6cd 0453ed4edbe15f7703f9c74c4dbfeb6a9165f7b8ab046cba178d620bd4171c78 a0a8c6b09d7951403ae8b5ac751f9327941a9d71e9ceca4926364669786a15d3 2397795012e8a8ce8e19d76d0175947862affc92e7e0d60f9005b7b83148aadf 67b8c184cd20d2b1ea8ca53cfb283c18f060227955f4a25d2a66858a5f103248 41195fc6a36f2c01e140200360b75c8ab5f8dfdb7981f6e0541c4d77a47e9632 50571d40ac6b810405db3996fbd42458b1cc3ba8e32b93f106232b76e7bc2ab9

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