All-network search
MainnetChipnetTestnetTestnet3TestnetTestnet4TestnetGalt Block Explorer search
Matched 1 configured network for this block hash or transaction id. 3 configured networks were unavailable, so the search is incomplete.
This search spans every configured BCH network. Paste once; each match opens the canonical page on its chain.
- Query type
- Block hash or transaction id
- Chains searched
- 1 of 4
- Matches
- 1
- Not checked (unavailable)
- 3
This search is incomplete: 3 chains were not checked because the lookup was unavailable, so the answer there is unknown, not "no match".
A chain that did not answer is not counted as searched.
Input shape
00000000000000000133be70765500255f1125920e1a8d132bdf33bdeec9d4ccA 64-character hex value: a block hash or a transaction id.
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 972781 mined at 1791956296 will open on the canonical block-hash route.
- ChipnetTestnetUnavailable
Not checked: Network lookup failed while checking the hash: Not Found for Backend request: Requested block not found (Requested block not found)
- Testnet3TestnetUnavailable
Not checked: Network lookup failed while checking the hash: Not Found for Backend request: Requested block not found (Requested block not found)
- Testnet4TestnetUnavailable
Not checked: Network lookup failed while checking the hash: Not Found for Backend request: Requested block not found (Requested block not found)
Results1 match
Grouped by type, then chainBlocks1 chain
- MainnetMatchBlock
Block 972781 mined at 1791956296 will open on the canonical block-hash route.
/mainnet/block/00000000000000000133be70765500255f1125920e1a8d132bdf33bdeec9d4cc
Not checked — unavailable3
Incomplete: 3 chains were not checked- ChipnetTestnetUnavailable
Not checked — unavailable: Network lookup failed while checking the hash: Not Found for Backend request: Requested block not found (Requested block not found)
- Testnet3TestnetUnavailable
Not checked — unavailable: Network lookup failed while checking the hash: Not Found for Backend request: Requested block not found (Requested block not found)
- Testnet4TestnetUnavailable
Not checked — unavailable: Network lookup failed while checking the hash: Not Found for Backend request: Requested block not found (Requested block not found)
Cross-network search playbook
Search first, pick the chain second
- Wallet userNetwork directoryPaste a txid once and let every configured network be checked.
- Wallet userSite transaction feedKeep watching confirmed payments across chains.
- ResearcherCompare networksCompare hits side by side instead of retyping.
- ResearcherRecent activitySee which networks are moving right now.
- OperatorSite statusCheck freshness before citing a result.
- OperatorSite OpenSearchReuse the declared search template.
- Data userllms.txtFollow the published route guide.
- Data userSitemap indexDiscover canonical detail pages and feeds.
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.