Skip to content

API reference

Base URLs

Every method below is a POST to {base}/{method} with a JSON body, a publishable key (nxp_…) in the Authorization: Bearer header, CORS open. The full-node RPC and the indexed API share the same host. Testnet11 is served by Coinset without a key.

  • Mainnet: https://api.nodexch.com
  • Testnet11: https://testnet11.api.coinset.org
  • WebSocket (peak and transaction events): wss://api.nodexch.com/ws?key=nxp_…&events=peak,transaction,reorg,dashboard,vault

Full OpenAPI specs: coinset.org/openapi/full_node_bundled.json and coinset.org/openapi/coinset_bundled.json. Endpoints marked "any full node" work against your own node too — see Settings → custom node.

Chain and mempool

  • Peak height and hash, mempool size and cost, block max cost, difficulty, sync state.

  • Fee-per-cost estimate for one or more target confirmation times.

  • Every spend-bundle id currently in the mempool.

  • Every pending spend bundle in full. Large (tens of MB); the app diffs it against ids it already has instead of refetching whole.

  • One pending spend bundle by id.

  • Pending spend bundles touching a coin.

  • Estimated netspace between two header hashes.

Blocks

  • Block records in a height range, end exclusive. Coinset caps a single call at 1,000 records.

  • One block record by height.

  • One block record by header hash.

  • The full block (generator info, reward claims) by header hash.

  • Coin spends in a block (custom-node fallback for coin flow).

  • Coins created and removed in a block, for the coin-flow view.

  • Semantic transaction summaries confirmed in a block, paginated.

Transactions (indexed, Coinset only)

  • One semantic transaction summary by spend-bundle id.

  • Transaction history for an address's puzzle hash, paginated, newest first.

  • Pending transactions for an address.

  • Transaction history for a CAT asset id, paginated.

  • Transaction history for an NFT.

  • The transaction that created and, if spent, removed a coin.

Coins

  • One coin record by coin id.

  • Coin records by a list of coin ids.

  • Coin records paid to a puzzle hash.

  • Coin records by memo hint (how wallets find their own coins).

  • Coin records created by a list of parent coin ids.

  • The reveal and solution a coin was spent with.

  • Memo strings attached to a coin's spend.

  • Coin semantics (kind, asset id) when Coinset can classify it.

  • Submit a spend bundle to the mempool.

Balances and assets (indexed, Coinset only)

  • Confirmed and pending XCH balance for a puzzle hash.

  • CAT balances for a puzzle hash.

  • NFT count for a puzzle hash.

  • Singleton (NFT/DID) lineage by launcher id.

  • The current unspent coin of an NFT.

Offers, clawbacks and reorgs (indexed, Coinset only)

  • Lifecycle state of one offer by id: both sides, makers, the taking or cancelling transaction.

  • Offers made from a puzzle hash, one lifecycle status per call.

  • Offers that offer or request a CAT.

  • Offers that offer or request an NFT.

  • Clawback coins sent to a puzzle hash, with timelock and whether the sender can still revoke.

  • Chain reorganisations Coinset detected, newest first.

  • Mempool-style item (coin spends, additions, removals) of a bundle even after it left the mempool.

Other data

CAT names, tickers and icons come from Dexie's public registry: GET https://api.dexie.space/v1/assets?type=cat (paginated, 100 per page), icons at https://icons.dexie.space/{asset_id}.webp.

NFT metadata and images come from MintGarden: GET https://api.mintgarden.io/nfts/{nft1_id}.

Embeds and badges

Drop-in widgets for pools, wallets and community sites. Each is a small static page (under 15 KB of script, no framework) that fetches Coinset directly from the visitor's browser, so nothing about your visitors reaches us. ?theme=dark|light picks the colours, &network=testnet11 switches network. They may be framed from any origin.

  • Block queueThe projected next blocks and the last three transaction blocks.preview
    <iframe src="https://mempoolxch.space/embed/blocks.html?theme=dark" width="100%" height="120" style="border:0;border-radius:10px" loading="lazy" title="Block queue · mempoolxch.space"></iframe>
  • Fee cardsThe node's fee estimate for next block, ~5 and ~10 minutes.preview
    <iframe src="https://mempoolxch.space/embed/fees.html?theme=dark" width="100%" height="130" style="border:0;border-radius:10px" loading="lazy" title="Fee cards · mempoolxch.space"></iframe>
  • Mempool occupancyBundles waiting, cost used of the node's capacity, total fees.preview
    <iframe src="https://mempoolxch.space/embed/mempool.html?theme=dark" width="100%" height="150" style="border:0;border-radius:10px" loading="lazy" title="Mempool occupancy · mempoolxch.space"></iframe>
  • Transaction statusPending, confirmed or removed for one transaction id.preview
    <iframe src="https://mempoolxch.space/embed/tx.html?id=<tx id>&theme=dark" width="100%" height="90" style="border:0;border-radius:10px" loading="lazy" title="Transaction status · mempoolxch.space"></iframe>
  • SVG badgeA shields-style image for READMEs and pages that cannot run scripts; served by mempoolxch.space, cached for a minute.
    ![Chia tx status](https://mempoolxch.space/api/badge/tx/<tx id>.svg)

Rate limits and fair use

These are Coinset's, Dexie's and MintGarden's endpoints, not ours: we cannot set their rate limits, and none are published as of this writing. Be considerate — cache what you fetch, batch where an endpoint allows it (for example get_block_records' height range, capped at 1,000 per call), and avoid polling faster than roughly once per block (~18–20 s on mainnet).

mempoolxch.space's own Terms of use still govern this site itself (uptime, acceptable use of the pages you load here); using Coinset, Dexie or MintGarden directly is between you and them.