First visit confidence
Bitcoin Cash Testnet4 is fully server-rendered with hard links, so the first useful click works even when scripts are disabled.
Start hereBlock receipt
Bitcoin Cash Testnet4 block proof, condensed for sharing
This page strips block proof down to the shortest trustworthy handoff: canonical route, receipt route, raw block route, timing facts, and the next click for deeper investigation.
0000000005a40b27e44cc8186cd46ff15e8b42e997920ae2f91a8979fc3836f6
Human-safeShare this route when someone mainly needs timing, confirmations, and canonical follow-up links.
Machine-safeRaw hex, canonical routes, and status links remain one click away from the same proof surface.
Honest scopeThis receipt summarizes what the explorer can prove directly without inventing hidden history or external-database claims.
Fast block proof
Counterparty
Receipt page
Use this page when a person needs one clean screen with block timing, confirmation depth, and canonical routes.
Shareable proof facts
Block receipt facts
When to escalate
Researcher
Inspect transactions
Move from this receipt to the full block page when you need the visible transaction table, coinbase note, or page analytics.
Operator
Check freshness
Look at status and chain stats before making a freshness-sensitive claim about this block or the current tip.
Visible transactions on this page
Open full block- 7039d98662adb41cea4bdc796ffbd518eb311091de84603a0a697cfd12d002f1
- 6688559c2124944c540a24100e32d685eb940e9d463a456ffed56cabae9b8046
This receipt shows a small sample only. The full block page keeps the complete visible transaction table and pagination controls.
Block receipt FAQ
What this compact proof page is for
This route exists to reduce friction when a full block page is more detail than the recipient needs.
When should I share this receipt page instead of the full block page?
Use the receipt page when a person mainly needs the block hash, height, time, confirmation depth, and canonical follow-up routes. Escalate to the full block page for transaction-by-transaction inspection.
Is this receipt page enough for machine verification?
It is the human-friendly summary. Machines should still use the raw block route, canonical block page, status page, feeds, sitemap, or llms.txt as appropriate.
Why does the receipt mention visible-page scope?
Block analytics on the main block page can be intentionally limited to the currently rendered transaction page. The receipt repeats that honesty instead of pretending the explorer computed more than it actually did.