StatusConfirmedConfirmed on-chain
Confirmations2,661Based on the current tip
Output total262.42512745 BCHAcross all visible outputs
Outputs2120 tokenized outputs
Block949,8950000000000…8d623f1f
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.
2b2ecfd3891c9aeebf730ce9fcee136bbdafc4b51cb7dc694bdac58a9da8b379
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 2,661 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
Confirmations2,661
Block949,895
Outputs21
Output total262.42512745 BCH
CashToken outputs20
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 | 118.67461041 BCH | 30c67982a271a3bd332aa0464ad8b69232cc12c231f28cfc0eac06da774aebab Custom script | CashTokenFT5,806,637 |
| 1 | 86.90852943 BCH | 4e9bb2ae651f34c3c83f3b6f2aa984fe10b8f2d4d41f99bdcf9f088eb5e70622 Custom script | CashTokenFT4,252,353 |
| 2 | 13.37335384 BCH | c518288a926db319e5d6be1f4803ada016258a576a0c23134293726c5455701f Custom script | CashTokenFT654,345 |
| 3 | 10.93780857 BCH | 9f8ad71d79667ade63a4e8e090cb50c82d5e68351fc0cd03c75290ff11c1c4ce Custom script | CashTokenFT535,178 |
| 4 | 9.75084218 BCH | a148bc0d703f761ebe1950f8ef7dad87ed7292eb8b6b2d3d8b6635e506645de3 Custom script | CashTokenFT477,100 |
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.