Help

Why mempoolxch.space

A handful of things this build does that other Chia explorers we compared against do not, as of the last check:

A Sage in-app wallet page: your pending transactions on the dashboard with queue position and a confirmation chime.
Projected next blocks packed the way the node actually fills them (cost-ordered), not just a queue length.
Every CAT gets a name and icon from the Dexie registry, on every page that shows one, not just a lookup page.
Accessibility checked on every route: automated axe AA passes and a full keyboard walk, in the test suite, not just claimed.
Open source under MIT, one Docker image, deployed the same way documented in the repo.

The full feature-by-feature comparison, including what still favours the competition, is kept up to date in the competitor matrix (wiki).

Reading the dashboard

What are the blocks left of the dotted line?

They do not exist yet. They are the next transaction blocks the way the network is likely to fill them: every pending spend bundle, sorted by the fee it pays per unit of cost, packed into blocks of 11 billion cost. The block right next to the line is the next one; the ones further left come after. Each shows the typical fee rate inside, the fee range, the total fees, how many spend bundles it holds and roughly when it will be farmed. Click one to see what is in it.

And the blocks on the right?

The transaction blocks that were just confirmed, newest first, with their fees, reward claims, age and the farmer who won them. Chia farms a block every 18.75 seconds on average but only every third one carries transactions; the small +N markers count the empty ones in between.

Why is the fee estimate usually 0?

Chia is not Bitcoin. Fees are paid per unit of CLVM cost, and the mempool accepts spends with no fee at all as long as it has room. The capacity bar shows how full it is (ten blocks worth of cost). When it fills up, paying a fee moves you ahead of the 0-fee backlog, and the cards show the rate that gets you into the next block, in five minutes or in ten.

What does "Next block" show?

The composition of the block about to be farmed: one cell per spend bundle, sized by its cost, coloured by its fee band, outlined by asset kind. Use the chips to spotlight XCH, CAT, NFT, offer or DID spends. Hover a cell for details, click to open the transaction.

What is the mempool graph?

How much cost is waiting, split by fee band, over the last two hours. It is sampled by your browser while the page is open, so it starts when you first opened the app.

Finding your transaction

What can I paste into the search box?

A transaction (spend bundle) id, a block height or header hash, an xch or txch address, a coin id, a CAT asset id, an nft1 id or a did:chia: id. A plain word is looked up as an XCHandles handle and searched as an NFT or collection name at the same time. Press / anywhere to jump to the box. If a 64-character hex id could be several things, the app checks the mempool, transactions, coins and blocks and shows you the candidates.

What is a handle?

XCHandles (xchandles.com) is a name registry on Chia: a handle such as @maximedogawa is a registry slot that resolves to a name NFT, and that NFT's address is where a payment to the name goes. Its page shows what it resolves to today, who holds it and when the registration runs out, and it can be watched like an address. Handle data comes from the registry's own read-only API, mainnet only.

I sent a transaction. Where is it?

Paste its id or your address. A pending transaction shows which projected block it sits in and an estimated time; once confirmed it shows the block, confirmations and what moved between which addresses. The address page lists your pending transactions at the top and refreshes on its own.

Why does a coin page say "not classified"?

The classification comes from Coinset's coin details, which are not always available. Plain XCH coins rarely need one; CAT and NFT coins still link to their asset pages from the transaction view.

Using it inside the Sage wallet

How do I install it?

In Sage 0.13 or newer open Apps → Install from URL and paste https://mempoolxch.space. Sage downloads and verifies the app; from then on it follows your wallet's network and theme, and a My wallet entry opens your own address page once you allow it to read your receive address.

Why does the network switch look disabled?

Inside Sage the app always shows the network your wallet is on.

Where does the data come from inside Sage?

Everything that is yours comes from the wallet itself: balance, sync state, pending and past transactions, your coins, whether an address is yours, and the XCH price. Sage is a light wallet, and its app bridge offers no node queries (no peak, mempool or block lookups), so the mempool, blocks and other people's addresses still come from the chain endpoint in Settings, Coinset by default or a node you whitelist.

Using your own node

Do I need a node?

No. By default everything comes from Coinset's public Chia full node and its index, which also powers the live updates, address history and CAT/NFT pages.

I want to use mine anyway.

Settings → Full-node RPC endpoints accepts any Chia full-node RPC over HTTPS. A stock node listens on https://localhost:8555 with client-certificate TLS and no CORS headers, which a browser cannot talk to directly, so put a small proxy in front of it:

# Caddyfile
:8556 {
  reverse_proxy https://localhost:8555 {
    transport http {
      tls_client_auth ~/.chia/mainnet/config/ssl/full_node/private_full_node.crt ~/.chia/mainnet/config/ssl/full_node/private_full_node.key
      tls_insecure_skip_verify
    }
  }
  header Access-Control-Allow-Origin *
  header Access-Control-Allow-Headers content-type
  @options method OPTIONS
  respond @options 204
}

What changes with my own node?

The app polls instead of streaming and fetches the raw mempool itself. Coinset-only features (semantic transaction summaries, address history, CAT and NFT history) are hidden with a note. Everything block, coin and mempool related keeps working.

Where do live updates come from?

The connection pill (hover it), the footer and Settings name the channel your tab is on. There is no server in between: this site only hosts the app itself, and every tab talks to the chain endpoint directly.

Live stream: updates arrive as they happen. The usual mode.
Polling: the app checks for updates every few seconds. With your own node, or while the live stream is unavailable.