All chains

All-network search

MainnetChipnetTestnetTempnetTestnetTestnet3TestnetTestnet4Testnet

Galt Block Explorer search

Matched 2 configured networks for this block height.

This search spans every configured BCH network. Paste once; each match opens the canonical page on its chain.

Query type
Block height
Chains searched
5 of 5
Matches
2
What the input is, and where it was looked up

A chain that did not answer is not counted as searched.

Input shape

972857

A block height (6 digits).

The server reports one result per chain. A 64-character hash may resolve as a block or transaction; this page does not expose each internal lookup.

Chains, in configured order

  • MainnetMatch

    Block 972857 resolves to 000000000000000000444b6f0eaf0db7d9f7c33a01a35f0128a7f62de2d0a2cc. The detail route will canonicalize to the block hash.

  • ChipnetTestnetNo match

    Block 972857 is not known on this network.

  • TempnetTestnetNo match

    Block 972857 is not known on this network.

  • Testnet3TestnetMatch

    Block 972857 resolves to 0000000000334a270b0f35b4b2cecb721ffe146f0fc8668bdf3e3a46d3ac2528. The detail route will canonicalize to the block hash.

  • Testnet4TestnetNo match

    Block 972857 is not known on this network.

Results2 matches

Grouped by type, then chain

Blocks2 chains

Other chains searched3

Cross-network search playbook

Search first, pick the chain second

Search FAQ

What this lookup page promises

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.