First visit confidence
Bitcoin Cash Mainnet is fully server-rendered with hard links, so the first useful click works even when scripts are disabled.
Start hereBlock receipt
Bitcoin Cash Mainnet 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.
000000000000000001870e115fa2d53fd65c2b2014d4c790d7306ef4a6d21b84
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.
Height471,792Canonical block shortcut
Confirmations475,569Returned directly with the block
Timestamp2017-06-18 08:39:21 UTCHeader time exposed by Flowee
Transactions1,121All tx ids currently visible on this block page
ScopeVisible metrics cover only the currently rendered transaction page to stay safe on shared public Flowee nodes.Receipt repeats renderer honesty
Serving nodemainnet-node-1Tip 947,360
Suggested handoff wording
What to say when you share this proof
Use these short statements when another person needs the answer first and the forensic routes second.
For a person
On Bitcoin Cash Mainnet, block 471,792 is visible at 2017-06-18 08:39:21 UTC with 475,569 confirmations.
For a ticket
Start with the receipt route, then keep the canonical block page and raw block hex ready only if the reviewer asks for deeper proof.
Best follow-up
Use the full block page for transaction context, or network status when freshness and tip movement matter.
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- 8b61e55b154a4163b00f296e2a3017b8e2a4e5062e6e71648e65260d712e230c
- 987d2d5d4007d458c990d16779f71b265132ab652ae46bb340c26680e3ef0836
- 99cdfac5d6469a2c423d7789c4b6a37857c76f7289440d60ad3fb4b4b9f046c0
- 4ed57f3f3bf115a7b1576af53b0f75551ea4afa2f1155db4bff26f20a37ec21a
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.