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

af20391a1220c933856c94de807df3ef212337d3cabbeb354982dfc701d07f42

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/af20391a1220c933856c94de807df3ef212337d3cabbeb354982dfc701d07f42
Raw proof
/mainnet/tx/af20391a1220c933856c94de807df3ef212337d3cabbeb354982dfc701d07f42/raw
Receipt page
/mainnet/tx/af20391a1220c933856c94de807df3ef212337d3cabbeb354982dfc701d07f42/receipt
Network
Bitcoin Cash Mainnet
Status
Confirmed on-chain
Containing block
630,935 · 000000000000000001db307cb5d8d46f7b0595f031850eabf7f7df9d9a78152e
Block time
2020-04-15 14:51:21 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 630,935.

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.25009626 BCH to bitcoincash:qrjc9yecwkldlhzys3euqz68f78s2wjxw5h6j9rqpq.

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/af20391a1220c933856c94de807df3ef212337d3cabbeb354982dfc701d07f42/receipt
Machine-friendly proof
/mainnet/tx/af20391a1220c933856c94de807df3ef212337d3cabbeb354982dfc701d07f42/raw
Containing block
/mainnet/block/000000000000000001db307cb5d8d46f7b0595f031850eabf7f7df9d9a78152e
Status context
/mainnet/status
Prevout coverage
Coinbase
StatusConfirmed
Inputs1
Outputs2
Output total6.25009626 BCH
Resolved input totalCoinbase
Prevout coverageCoinbase
Fee
Fee rate
CashToken outputs0
Raw size206 B

Settlement analysis

Resolved prevout coverage
Coinbase
Resolved prevout total
Coinbase
Output total
6.25009626 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: “i^BJ/HuoBi/mm'eYeo=4NA^vV3Dex !1^…”
View unlocking script
0397a00904691f975e424a2f48756f42692ffabe6d6d2765888159656f3d061b344eb941f35eb2d388d9ae7656e53313db446589b3d3080000009cba789e20218b9cf0da315eb8dd0500

Outputs

#AmountAddressScriptTokensSpent
06.25009626 BCHbitcoincash:qrjc9yecwkldlhzys3euqz68f78s2wjxw5h6j9rqpq
P2PKH25-byte pay-to-public-key-hash output
View locking script
76a914e582933875bedfdc448473c00b474f8f053a467588ac
e8c9f97a35325c4c08b16aa96c2c1a61ec80144167535fb13ac622971567484f in block 631,051
10.00000000 BCH8ee1836429a0be8d7ca5505f62e866281b1bed8b9f3170fa4d2a103306e27284
OP_RETURNMetadata output: “$m;2U2s'ZK*”
View locking script
6a24b9e11b6d14ca03cfa7e43b3255f3a6c389b03273edbb0ffdab279babe35a4b91bd2a038b
Spent

Raw transaction hex

Open as text/plain
02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4a0397a00904691f975e424a2f48756f42692ffabe6d6d2765888159656f3d061b344eb941f35eb2d388d9ae7656e53313db446589b3d3080000009cba789e20218b9cf0da315eb8dd0500ffffffff02dae34025000000001976a914e582933875bedfdc448473c00b474f8f053a467588ac0000000000000000266a24b9e11b6d14ca03cfa7e43b3255f3a6c389b03273edbb0ffdab279babe35a4b91bd2a038b00000000