All-network search

Bitcoin Cash (BCH) Block Explorer search

Matched 1 configured network for this block height.

This search spans every configured BCH network. Paste once, then choose a chain when you already know it.

Configured networks3

Matches1

Query typeBlock height

Default path/mainnet

Bitcoin Cash Mainnet

mainnet

Result: Match
Type: Block
Target: /mainnet/block/956599
Notes: Current best height is 956831. The detail route will canonicalize to the block hash.

Open result Open receipt Network home Status

Bitcoin Cash Chipnet

chipnet

Result: No match
Type: Above current tip
Target: /chipnet/blocks/latest
Notes: Current best height is 311752, so block 956599 is not known on this network yet.

Search this network Network home Status

Bitcoin Cash Testnet4

testnet4

Result: No match
Type: Above current tip
Target: /testnet4/blocks/latest
Notes: Current best height is 311747, so block 956599 is not known on this network yet.

Search this network Network home Status

Cross-network search playbook

Different users, same simple lookup surface

This search page should feel obvious whether you are starting from a wallet notification, a block hash pasted into chat, or an automation workflow that still needs a human-auditable destination.

Wallet user

I can search first and decide the network second

A payment tracker should not have to guess which configured BCH network a txid belongs to before getting help.

1
Paste the txid onceLet the site test every configured network.
2
Confirm the matching networkUse the path segment and route result to orient yourself.
3
Open the site tx feedMove from one-off lookup to ongoing machine-readable updates.

Researcher

I can compare hits instead of retyping

Search results stay split by configured network so a shared hash or height can be investigated without losing context.

1
Compare networksUse side-by-side context when multiple chains matter.
2
Open recent activityCheck which networks are moving right now.
3
Inspect site statusVerify freshness-sensitive operations before citing results.

Operator

Search accepts common BCH values

The search page documents what is recognized, including wallet-style BCH payment URIs, when query pages are noindex, and where canonical detail pages begin.

1
Open site OpenSearchReuse the declared search template instead of inventing routes.
2
Read llms.txtFollow the route guide.
3
Open sitemap indexDiscover canonical detail pages and feeds at deployment scope.

Search FAQ

What this lookup page promises

The all-network search route is meant to feel simple for humans and precise for machines, including wallet-style BCH payment URIs.

Why can this page be indexed when query-result pages are noindex?

The empty search helper is a useful navigational page, but arbitrary query-result pages should not consume browser budget. Canonical detail pages remain indexable and linkable.

What kinds of values are recognized here?

The search helper recognizes decimal block heights, 64-character hexadecimal block hashes or txids, Bitcoin Cash cashaddr-style addresses, and wallet-style Bitcoin Cash payment URIs. Matching results then link to canonical network routes.

Why search all networks instead of forcing one chain first?

Many users start from a txid or address copied out of band and do not yet know which configured BCH network they need. This page removes that friction.