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.
33d9540fa68977175bc32d734cd753b8ffbd4c8c8ae77d0692f99ac3bb96fcef
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
Confirmations250,650Based on the current visible tip
Output total0.02998076 BCHAcross all visible outputs
Outputs6No CashToken outputs visible
Block696,6250000000000…2ca79a2f
Serving nodemainnet-node-1Tip 947,274
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 250,650 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
Confirmations250,650
Block696,625
Outputs6
Output total0.02998076 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.02993076 BCH | bitcoincash:qprhw0hpw29wr4tcwxfex5g4khfskz2gac00tmp8q7 | — |
| 1 | 0.00001000 BCH | 73ea4c89240cc2681b996a36246cbfae1b25d8e372299ef8b7496cea9e9628e2 Custom script | — |
| 2 | 0.00001000 BCH | 8f36442286919ef68dfcc73c5e487e7abd762c7087d23f640ef535664225d21b Custom script | — |
| 3 | 0.00001000 BCH | 3a935759c4649f03a81287289774038f7c5df51a6ec5c909c0cb32108e44cdd0 Custom script | — |
| 4 | 0.00001000 BCH | 6406e712dc6d8aea7037fb975e0391f4db9f3bd34432b06361fc62b0ccbf149a Custom script | — |
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.