StatusConfirmedConfirmed on-chain
Confirmations3,368Based on the current tip
Output total0.03722402 BCHAcross all visible outputs
Outputs76 tokenized outputs
Block949,1880000000000…dfeca422
Serving nodemainnet-node-1Tip 952,555
Verification 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.
531a5387d94de4119ea01e2fab755a7ca91613f432917a97b8f45966d99b8dd5
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.
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 3,368 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
Confirmations3,368
Block949,188
Outputs7
Output total0.03722402 BCH
CashToken outputs6
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 current tables.
Inclusion path for this tx
Download the merkle proof in hex or binary format.
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, raw transaction hex, and merkle proof.
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.01372883 BCH | e7ff0e7768c8ce951d718b284af9fd64a96ac8a7ae8b9c9b0019512d32d75989 Custom script | CashTokenFT222,462,364 |
| 1 | 0.00264219 BCH | 9a341f7b6d330cf28fbff9d55ae42ddee2487b6f7360e9b3aa074ef53179aaa9 Custom script | CashTokenFT42,814,185 |
| 2 | 0.00160825 BCH | d8169e90866ebac05cc99690c50c7059a55a4937ee34b8cd1f47fefb3f85409c Custom script | CashTokenFT26,060,182 |
| 3 | 0.00132089 BCH | 0f716828ab24f4f6fa65e37ed8966724459ca393ec384583753cf6b27bbb965a Custom script | CashTokenFT21,403,699 |
| 4 | 0.00119265 BCH | 036932639d3b6ad576ffcd326438ba867ea22f2bcb4c7b800c83be62f3eaa771 Custom script | CashTokenFT19,326,227 |
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.