Galt Block ExplorerSEO-first Bitcoin Cash explorer powered by FloweeBridge

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
Chain start here

Bitcoin Cash Mainnet in the first minute

This page is the shortest orientation route for Bitcoin Cash Mainnet. It tells a wallet user what to click first, a researcher where live history begins, an operator how to establish trust, and an AI agent which machine-safe surfaces to prefer.

Verify a paymentSearch this networkNetwork homepageLatest blockSampled txStatus
Need a quick answerUse verify or the receipt routes when someone only needs the shortest trustworthy proof path.
Need detailOpen the canonical block or transaction page for decoded tables, analytics, and raw routes.
Need machine safetyFeeds, sitemap, OpenSearch, raw routes, and llms.txt remain declared public surfaces.
Search live height 946,897Search best block hashSearch sampled txStay on start hereRead llms.txt
Best height946,897
Recent tx sampleReady
Bounded tx window946,897 → 946,897
AI route guide/llms.txt
What do you have in hand?

Choose the task, not the menu

Txid

Prove one payment

Paste the txid when you need the shortest route to confirmations, outputs, fees, receipts, and raw evidence.

Verify·Sampled tx
Address or BCH URI

Show receipt or activity

Search or verify the address to inspect bounded history, unspent outputs, locking script evidence, and the address receipt page.

Search·Verify
Block reference

Prove inclusion

Use the block route when someone shared a height or block hash instead of a txid.

Latest block·Browse blocks
Need backend trust

Establish freshness first

Operators and support teams often need failover and serving-node visibility before citing anything else.

Status·Mempool
Proof ladder

Move from human-readable confirmation to machine-readable evidence

Human proof

Start from a live payment receipt

The receipt page is the shortest support-safe summary, while the canonical tx page keeps full decoded detail one click away.

Open tx receiptOpen full tx
History proof

Open the newest block receipt

The block receipt is the shortest proof of chain history, and the full block page keeps decoded transaction context nearby.

Open block receiptOpen full block
Operational proof

Check status before freshness-sensitive claims

Status exposes reachability, cooldowns, and serving-node context, while stats explain cadence and subsidy context for the same chain.

Network statusChain stats
Machine proof

Start from declared discovery

Sitemap, feeds, OpenSearch, raw routes, and llms.txt remain preferred entry points for crawlers and agents.

Network sitemapTransaction feed
Persona walkthroughs

The first three clicks should feel obvious

Wallet user

I answered did this payment happen?

The route should move from uncertainty to a shareable proof without forcing the user to learn the whole explorer first.

  1. 1
    Paste the txid, address, or BCH URIUse the network verification guide when you already know the chain.
  2. 2
    Open the transaction receiptShare the condensed proof page when someone mainly needs status, time, and canonical links.
  3. 3
    Open raw txFinish on raw evidence that matches the rendered receipt and transaction page.
Researcher

I can understand recent chain history

The chain-specific start page should answer what is happening now, then show where the deeper history routes begin.

  1. 1
    Open the newest blockStart from the canonical tip route for the current chain.
  2. 2
    Browse older blocksWalk backward with crawlable pagination instead of infinite scroll.
  3. 3
    Open chain statsContinue to cadence, subsidy, halving, and other chain-level context.
Support / operations

I can hand off proof safely

When another team or counterparty is involved, the shortest calm route is usually better than the densest one.

  1. 1
    Check status firstVerify backend trust and serving-node context before making freshness-sensitive statements.
  2. 2
    Share the receipt pageSend a concise proof page before escalating to the full transaction tables.
  3. 3
    Keep the block receipt handyKeep the block proof path ready in case someone questions confirmation depth or inclusion.
AI / crawler

The route family is easy to learn

Automation should start from published discovery routes, then escalate to canonical detail paths.

  1. 1
    Read llms.txtStart from the plain-text route map.
  2. 2
    Open the network sitemapDiscover detail, feed, and diagnostics routes without guessing.
  3. 3
    Open OpenSearchReuse the published search template for this specific chain.
Start-here FAQ

Questions this chain-specific page should settle fast

A great first-minute page should remove both confusion and overconfidence.

What is the best first route when I already know the network?

Use the chain-specific verify or search route first. They keep you on the correct network while still guiding you toward the canonical detail or receipt page you actually need.

Why are receipt pages promoted so heavily here?

Because many real-world conversations do not need the full transaction or block tables immediately. Receipt pages give a calmer proof handoff while keeping raw and full-detail routes one click away.

Can this page prove full address history or an infinite balance?

No. The explorer stays honest about bounded windows and database-free coverage. When something is partial, the page should say so explicitly instead of pretending otherwise.

Where should an AI agent begin on this chain?

Start from the network sitemap, feeds, OpenSearch, llms.txt, and status page. Those routes declare the public contract more safely than reverse-engineering the rendered HTML.