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 here

Machine discovery

Feeds, OpenSearch, sitemap, and llms.txt stay visible as canonical entry points for agents and integrations.

Open llms.txt

Operational honesty

Multi-node failover state, cooldowns, and serving-node details are exposed instead of hidden behind an admin-only view.

Inspect status

Crawlability first

Pages, feeds, and discovery routes are designed to be indexable, archivable, and easy to mirror without JavaScript.

Open sitemap
Transaction

Confirmed transaction

8041e8e03b4d5f360bfef50f85b16617684a9be9ad00a488eceffaa7b267c27e

Verification receipt

Shareable proof surface

Confirmed

This transaction page is designed to be the shortest human-readable proof path: one canonical route, one raw route, and one clear jump to the containing block when confirmation context matters.

Canonical route
/mainnet/tx/8041e8e03b4d5f360bfef50f85b16617684a9be9ad00a488eceffaa7b267c27e
Raw proof
/mainnet/tx/8041e8e03b4d5f360bfef50f85b16617684a9be9ad00a488eceffaa7b267c27e/raw
Receipt page
/mainnet/tx/8041e8e03b4d5f360bfef50f85b16617684a9be9ad00a488eceffaa7b267c27e/receipt
Network
Bitcoin Cash Mainnet
Status
Confirmed on-chain
Containing block
639,761 · 0000000000000000008efe2a8032edec989953c63de6ca4a83ee2d9c40d5f062
Block time
2020-06-15 22:52:20 UTC
Best next move

Choose the proof depth you need

Wallet user

I only need a yes or no

Stay on this page for confirmation status, amounts, and destination outputs.

Support desk

I need a citation-safe route

Share the canonical transaction URL first, then the block page if a counterparty questions confirmation context.

Auditor / AI

I need raw evidence

Use the raw transaction hex route and the containing block route together for independent verification.

Operator

I need freshness trust

Pivot to the network status page if node health or backend freshness needs to be cited alongside the transaction.

What this means

Readable transaction summary

This transaction is confirmed on Bitcoin Cash Mainnet in block 639,761.

Value movement

Follow the BCH

This is a coinbase transaction, so it creates new BCH rather than spending previous outputs.

Destination clues

Where outputs point

1 of the 2 outputs decode to direct BCH addresses on this page.

Largest visible output

Start from the biggest clue

Largest visible output: 6.25026469 BCH to bitcoincash:qqq97lqsg72x57uf62kne50a2hwk66keduuaz0atnm.

Spend state

How settled the outputs look

2 outputs already show a spender link or spent state on this page.

Proof handoff

Which link should you share next?

For human sharing, start with the receipt page. For deeper proof, add the containing block. For machine verification, pair the raw transaction with the canonical block route.

Human-friendly proof
/mainnet/tx/8041e8e03b4d5f360bfef50f85b16617684a9be9ad00a488eceffaa7b267c27e/receipt
Machine-friendly proof
/mainnet/tx/8041e8e03b4d5f360bfef50f85b16617684a9be9ad00a488eceffaa7b267c27e/raw
Containing block
/mainnet/block/0000000000000000008efe2a8032edec989953c63de6ca4a83ee2d9c40d5f062
Status context
/mainnet/status
Prevout coverage
Coinbase
StatusConfirmed
Inputs1
Outputs2
Output total6.25026469 BCH
Resolved input totalCoinbase
Prevout coverageCoinbase
Fee
Fee rate
CashToken outputs0
Raw size164 B

Settlement analysis

Resolved prevout coverage
Coinbase
Resolved prevout total
Coinbase
Output total
6.25026469 BCH
Inferred fee from prevouts
Reported node fee
Fee rate

Mempool diagnostics

First seen
Credibility
Double-spend proof
Raw endpoint
Open text/plain hex

Explorer decoding note

This page resolves previous outputs directly through FloweeBridge without any external database. When coverage is partial, the missing inputs are left clearly marked instead of being guessed.

Inputs

Prevout lookups resolved: 0 / 0
#Previous outputPrevout amountPrevout address or scriptUnlock typeUnlock previewUnlocking script
0CoinbaseCoinbase inputCoinbaseCoinbase data: “^hz/Binance/tE(”
View unlocking script
0311c30904a4fbe75e687a2f42696e616e63652f0519d79900007445ee280e00

Outputs

#AmountAddressScriptTokensSpent
06.25026469 BCHbitcoincash:qqq97lqsg72x57uf62kne50a2hwk66keduuaz0atnm
P2PKH25-byte pay-to-public-key-hash output
View locking script
76a914005f7c1047946a7b89d2ad3cd1fd55dd6d6ad96f88ac
26968ce9f67e7184a7766c1f8ba6ad66172d88fe43cf3a285039b8328808b5db in block 648,240
10.00000000 BCH7bcdb0d80f6f9e45821b33d6137faafe944287556f08f9100fb4f06fbc584aba
OP_RETURNMetadata output: “$m-#@d8q0Jkzz”
View locking script
6a24b9e11b6d8d2d8e1123078b0e40f88ead6438fb12a1afa971e2308b4a6b10967ae87a02e8
Spent

Raw transaction hex

Open as text/plain
02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff200311c30904a4fbe75e687a2f42696e616e63652f0519d79900007445ee280e00ffffffff02a5254125000000001976a914005f7c1047946a7b89d2ad3cd1fd55dd6d6ad96f88ac0000000000000000266a24b9e11b6d8d2d8e1123078b0e40f88ead6438fb12a1afa971e2308b4a6b10967ae87a02e800000000