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.
1ce57257cc308009894cadec5579fb0b28e1561c90f9c1f62f5cf133a50e200a
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
Confirmations43,384Based on the current visible tip
Output total113.82739029 BCHAcross all visible outputs
Outputs2019 tokenized outputs
Block903,8980000000000…6ed10243
Serving nodemainnet-node-1Tip 947,281
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 43,384 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
Confirmations43,384
Block903,898
Outputs20
Output total113.82739029 BCH
CashToken outputs19
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 | 2.33013802 BCH | 5982f209da1eaaf914ac9c3471f4ee55e0fad1eb76df004098e1c088e6f446ba Custom script | CashTokenFT107,866 |
| 1 | 4.14573812 BCH | 954271e0bb0be60a1b2e741860a1ecbe11871589e55fb82f9a43b169593192a6 Custom script | CashTokenFT191,915 |
| 2 | 2.39473488 BCH | 5982f209da1eaaf914ac9c3471f4ee55e0fad1eb76df004098e1c088e6f446ba Custom script | CashTokenFT110,856 |
| 3 | 23.06418143 BCH | 62116320b721689a2b7b80edf88003ac956bd42c1bc0b0d18fe4d3bfc7b48912 Custom script | CashTokenFT1,067,694 |
| 4 | 3.00327579 BCH | c23eead84471f62c9003568061b02f2e64c0b09f5b2e4b8b46b276d39206597a Custom script | CashTokenFT139,028 |
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.