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 hereBitcoin Cash Mainnet is fully server-rendered with hard links, so the first useful click works even when scripts are disabled.
Start hereFeeds, OpenSearch, sitemap, and llms.txt stay visible as canonical entry points for agents and integrations.
Open llms.txtMulti-node failover state, cooldowns, and serving-node details are exposed instead of hidden behind an admin-only view.
Inspect statusPages, feeds, and discovery routes are designed to be indexable, archivable, and easy to mirror without JavaScript.
Open sitemapThis 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.
dfd45fd7ba1ea77551fb070ede17c8cd4a67fdc21b516bc59dbfbaed4de7c944
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.
Share the receipt or canonical transaction route when a human needs the cleanest handoff.
Open the raw transaction hex when another system needs to verify bytes rather than rendered tables.
The containing block route is one click away for inclusion and confirmation-depth checks.
For stronger proof, pair this receipt with the containing block and raw transaction hex.
| # | Amount | Address or script | Tokens |
|---|---|---|---|
| 0 | 0.05059164 BCH | 2e5bfad1ee0bebabbdb5c916a5d2a46a469f9f890ed8626bd5ae2c92dc2fdb09 Custom script | Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 853,887,854FT: Yes |
| 1 | 0.04642187 BCH | b8b381dac4056d3e2bbfe47430d8c595c8aa7d95ffe9d6dccb41992c7de74b39 Custom script | Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 783,510,212FT: Yes |
| 2 | 0.02590557 BCH | 4cac20979564f407db7f232cc1225a6def71695f0cc6a6c2718d286b6107f64e Custom script | Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 437,235,197FT: Yes |
| 3 | 0.01817147 BCH | b60d1bbfab95f69e488a784c138826a133f584dbe0049231f93f7360ee245d9b Custom script | Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 306,698,892FT: Yes |
| 4 | 0.01106310 BCH | b8c575b306ab91487783261eed080c294ce6d61b42cc483b8ab9f35ae339afa7 Custom script | Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 186,723,488FT: Yes |
The full transaction page retains every input, output, prevout note, and raw script detail when deeper analysis is needed.
This route exists to reduce friction when a full transaction page is more detail than the recipient needs.
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.
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.
Confirmed transactions show confirmation count relative to the currently visible best height on this network. Mempool transactions stay clearly marked as pending.