Cross-network payment verification

Verify a BCH payment even when you are not sure which network to trust yet

This site-level guide is built for the first tense minute: a user arrives with a txid, address, block hint, or screenshot and needs the shortest path to a trustworthy page. Start wide, then narrow into the correct network with canonical links the whole way.

All-network search Compare networks Check site status Verify on default network Site tx feed

I have a txid but not the chainSearch once across every configured BCH network, then follow the matching canonical route.

I need a human-friendly proof linkLand on a canonical transaction, address, or block page first, then branch to raw evidence only if needed.

I need an automation-safe trailUse llms.txt, OpenSearch, feeds, status, and sitemap routes once the correct network is known.

Search default live height Search default best block Compare live networks Read llms.txt

A great first visit should make three things obvious: where to paste the evidence, where freshness is declared, and how to reach raw or machine-readable routes without starting over.

Live right now

Verification command center

3 / 3 live

Networks3Configured BCH explorer surfaces

Live now3Networks returning current data

Default path/mainnetBest choice when the chain is probably the default one

Agent route/llms.txtPlain-text discovery contract for scripts and LLMs

Open sitemap index Open OpenSearch

Pick the best first move

Different visitors, obvious starts

Wallet user

Check one payment

Paste a txid or address once, then let the site help you identify the right configured chain.

Search all networks·Default verify guide

Support desk

Find a citation-safe route

Move from a claim to a canonical page, then to raw or operational evidence without dead ends.

Site status·Site tx feed

Researcher

Orient before diving in

Compare chains, watch recent activity, and only then drop into the network that matters.

Compare·Recent activity

Data routes

Open public discovery

Use llms.txt, sitemap, and OpenSearch to find public routes.

llms.txt·Sitemap index

Cross-network proof ladder

How a first-time visitor should feel after one glance

The very first screen should tell users exactly how to win: paste once, confirm the correct network, then deepen the evidence only as far as needed.

Payment checker

I verified the payment without friction

The fastest path starts from uncertainty and still ends on a canonical chain-specific route.

1
Paste the txid or address onceUse the all-network search when the correct chain is still unclear.
2
Open the default verify guideUse the default network guide when the likely chain is already known.
3
Open the site tx feedContinue with a machine-readable confirmation surface if ongoing monitoring matters.

Support / operations

I can back my answer with operational honesty

The explorer should make freshness and backend trust cues visible before anyone needs to ask for them.

1
Inspect site statusCheck reachability, failover honesty, and network-level serving-node context.
2
Compare networksUse side-by-side context when the claim spans multiple configured chains.
3
Open sitemap indexCollect stable public routes for follow-up evidence or automation.

Data user

The route family is easy to learn

Public route lists make lookup and monitoring simpler.

1
Read llms.txtStart from the published route list.
2
Open OpenSearchReuse the declared site-wide search template.
3
Open site pages sitemapDiscover the most important site-level pages without guessing.

Choose a chain-specific verify guide

Verification launch pads by network

Bitcoin Cash Mainnet

Open the chain-specific verify guide

Use the dedicated verify guide for this configured chain when you already know where the payment belongs.

Verify on Bitcoin Cash Mainnet Search

Bitcoin Cash Chipnet

Open the chain-specific verify guide

Use the dedicated verify guide for this configured chain when you already know where the payment belongs.

Verify on Bitcoin Cash Chipnet Search

Bitcoin Cash Testnet4

Open the chain-specific verify guide

Use the dedicated verify guide for this configured chain when you already know where the payment belongs.

Verify on Bitcoin Cash Testnet4 Search

Evidence surfaces

Best routes for humans, tickets, and automation

Use case	Route	Reason
Search when the chain is unknown	All-network search	One paste lets the site test every configured BCH network before you choose a chain-specific detail page.
Compare before trusting	Compare networks	Tip height, cadence, mempool, halving, and health context stay visible side by side.
Operational honesty	Site status	Site-wide reachability, cooldowns, and network freshness cues stay public instead of hidden.
Machine-readable updates	Site transaction feed	The bounded feed is a stable surface for monitoring, polling, and lightweight automation.
Public data routes	llms.txt	LLMs and scripted consumers can begin from the explorer's declared public route guide.

Verification FAQ

What a first-time visitor should understand immediately

This page exists to remove hesitation for the most common block-explorer jobs.

What is the fastest first click when I only have a txid?

Use the all-network search if you are not certain which configured BCH network the tx belongs to. Once the correct network is clear, move into that chain's verify guide or canonical transaction page.

What if I only have a wallet address or screenshot?

Start from all-network search for the address, or compare networks and recent activity when the screenshot gives only partial context. The verify guides then narrow you into chain-specific evidence.

Why add dedicated verify guides when search already exists?

Because many users arrive anxious and task-focused. A great first impression is not just a search box; it is a page that explains the shortest trustworthy proof path for different kinds of visitors.

Where are the public data routes?

Start from llms.txt, sitemap, OpenSearch, and feeds. These routes list search, feed, and detail endpoints.