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 hereVerification receipt
Bitcoin Cash Mainnet payment proof, condensed for sharing
This receipt page strips the transaction view down to the shortest trustworthy proof trail: canonical link, receipt link, raw route, status, and containing block context when available.
6abdfe9e6ef482e11b4b8842acfacbfc1d0dfd25e4e63964a8f4e97ca534faea
Human-safeShare this page when someone needs a quick answer without parsing the full transaction tables.
Machine-safeRaw hex, block links, and status links remain one click away from the same canonical route family.
Honest by designPending transactions stay clearly marked as mempool entries instead of being overstated as settled.
StatusConfirmedConfirmed on-chain
Confirmations630,302Based on the current visible tip
Output total10.56222963 BCHAcross all visible outputs
Outputs6No CashToken outputs visible
Block316,9740000000000…b2ba99f5
Serving nodemainnet-node-1Tip 947,275
Suggested handoff wording
What to say when you share this payment proof
These sentence patterns keep the first explanation calm, bounded, and easy to verify.
For a person
This transaction is confirmed on Bitcoin Cash Mainnet with 630,302 confirmations.
For a ticket
Share the receipt route first, then add the canonical transaction page, raw transaction, or containing block only if the reviewer needs deeper evidence.
Best follow-up
Use the containing block when inclusion depth matters, and raw transaction only when someone needs byte-level verification.
StatusConfirmed
Confirmations630,302
Block316,974
Outputs6
Output total10.56222963 BCH
CashToken outputs0
What this receipt proves
Human-readable evidence summary
This receipt proves the transaction is visible on-chain for this network and links directly to the canonical block, raw hex, and status context needed for stronger verification.
Stable link for people
Share the receipt or canonical transaction route when a human needs the cleanest handoff.
Stable link for machines
Open the raw transaction hex when another system needs to verify bytes rather than rendered tables.
Use when confirmation depth matters
The containing block route is one click away for inclusion and confirmation-depth checks.
Know what this does not prove
For stronger proof, pair this receipt with the containing block and raw transaction hex.
Printable checklist
What to copy into a ticket, email, or PDF
Shareable proof facts
Transaction receipt facts
Visible destination preview
First outputs
| # | Amount | Address or script | Tokens |
|---|---|---|---|
| 0 | 0.29097000 BCH | bitcoincash:qz7zfxsd4s6s4q5yeq9v0gd3c07fj8r4ts3nww8aaw | — |
| 1 | 10.00000000 BCH | bitcoincash:qrh04x7qyz80qeszsdh420u92mm3w4t0yy9hew69pu | — |
| 2 | 0.00099580 BCH | bitcoincash:qrlg8jwgcwgkmy2nk5gkga2l3px8cqcy6q0shcdr93 | — |
| 3 | 0.25000000 BCH | bitcoincash:qq5jkm3z97edrs4zx683xgsuejsch297sse6q5cag4 | — |
| 4 | 0.01000447 BCH | bitcoincash:qzlnqlswpx3cgha9qfejkzqf6l3s2q46lg7wxhcj0t | — |
The full transaction page retains every input, output, prevout note, and raw script detail when deeper analysis is needed.
Receipt FAQ
What this compact proof page is for
This route exists to reduce friction when a full transaction page is more detail than the recipient needs.
When should I share this receipt page instead of the full transaction page?
Use the receipt page when a person mainly needs status, time, block context, and canonical links. Escalate to the full transaction page when they need to inspect inputs, outputs, or token detail.
Is this receipt page enough for machine verification?
It is the human-friendly summary. Machines should still use the raw transaction route, containing block route, status page, sitemap, feeds, or llms.txt as appropriate.
How is confirmation depth shown here?
Confirmed transactions show confirmation count relative to the currently visible best height on this network. Mempool transactions stay clearly marked as pending.