Docs
Open Console

Custom Explorers

Point U.CASH at your own block explorer API for balances and transaction detection - useful for private chains, rate-limit relief, or an explorer you trust.

How it works#

The custom explorer integration replaces the platform's default detection sources with your explorer's API, globally for the account. You configure URL templates plus JSON paths, and the platform reads balances, transaction lists, and single transactions straight from your explorer.

  1. Open Settings → Custom Explorer and turn it on
  2. Set the balance URL, transaction URL, and transactions-list URL, each with a JSON path to extract the value
  3. URLs take placeholders: {R} (address or transaction hash), {N} (coin code), {N2} (coin name)
  4. Set the unit divider: whole coins (Bitcoin/Ethereum/Dogecoin style) or base units (satoshi/wei style)
  5. Optionally set an address generator URL so your explorer can also derive fresh receive addresses

Example balance URL: https://explorer.example.com/api/balance/{N}/{R} with path result.balance.

Good to know

  • This setting is one explorer API for the whole account, not a per-coin link override
  • Buyer-facing "view transaction" links always point at the standard public explorer for the coin - the custom explorer governs detection, not display links
  • When the custom explorer is configured with a generator URL, it participates in address generation in the standard priority order (see Address Generation)
  • HTTPS only - the same safe-egress rules as webhooks apply

Fallback behavior#

If your explorer fails to answer, detection falls back to the platform's provider cascade so payments are never missed - your explorer is the primary, not a single point of failure. See Blockchain Nodes for the full detection architecture.