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-09-27T20:20:13.035Z
manifest sha256397c900851aef35d541debc6f7e3e000eb76356a41d3bc2505131120b607a585
html sha256f37773613c4ce361e221bc7fb8d0a355b9b2ad5989ed259979d7691f073247e0
proof⛓ timestamped on-chain
txidf5399fc0936bf6a84c352be6b3a295b3e3eecd65a79be56539fddc1ebd474adb
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 968,645 · 6,124 confirmations
SPV proof & how to re-verify it yourself
block height968645
block merkle roote37a5608511925568ad188b19c95752d33bbbeae5cf8a8346cfc2f203ebe6336
tx index360
branch (9)ad073d06ac4b5b6db412288a18366ab272c3a94237d8a4d0a558d794b564e027 169e246644ff222aa0def0180ba70514bf5addab0293dcd44953db33050c061c 3d73d0d329fea11f93d59f1790429cb274e2339cedca1f8d99fbefd1a8922c5f f0b5d586b61dcc24889a7393dc12318821dc24ab542dedac69948af4d35a0b37 6cd5200d7d0002265edb7c463c47ec1f2b5f789b8d7614837d4a3a4b59340dbb e7c43f5ce45e1876681ffd7ec4fc4a60730b1b1838bfc72e57e7116feb20de54 f97d5314ec4b2e4e425224377d609c301f06b00543af46a2faf3c2346212d49d 2d5faa066769745bc05b18155df28986a2cda1eb12e1965382b248a4181e2999 9ea65f13307af9e3b636a00b0c425f2ef9ebb33de9fb91532e329d886cc987a2

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