Read the chain

Explorer API

A plain REST API for transactions, balances, UTXOs and DRC-20 history — no indexer of your own required.

Live

Explorer exposes the indexer as a plain REST API — everything the Explorer web app itself renders is available to you at the same URLs. All endpoints below are relative to https://explorer.dogesoft.io/api.

Transactions

Endpoint	Description
GET `/tx/:txid`	Full transaction detail by txid.
POST `/tx/broadcast`	Broadcast a raw signed transaction to the network.
POST `/tx/pipeline`	Submit a signed move package to the pipeline broadcaster — see send pipeline.

Wallet & address reads

Endpoint	Description
GET `/wallet/address/:address/balance`	Confirmed DOGE balance for an address.
GET `/wallet/address/:address/utxos`	Spendable UTXO set for an address.
GET `/wallet/address/:address/drc20`	All DRC-20 balances held by an address.
GET `/wallet/address/:address/drc20/:tick/utxos`	DRC-20 carrier UTXOs for one tick.
GET `/wallet/address/:address/history`	Chronological transaction history — shape below.
GET `/wallet/address/:address/transfer_inscriptions`	Inscribed transfers for an address. Accepts `count`, `order`, `envelope` and `txid` query params.

{
  "address": "D8p...",
  "items": [
    {
      "txid": "a1b2...",
      "direction": "in",
      "counterparty_address": "D9q...",
      "block_height": 5822104,
      "amount_koinu": 420000000,
      "is_doginal": false,
      "confirmations": 142
    }
  ]
}

Amounts come back in koinu (1 DOGE = 100,000,000 koinu) — see terminology.

Indexer status

Endpoint	Description
GET `/status`	Indexer health and current sync height — poll this before trusting a "not found" response as final.

ℹ️

There's deliberately no dedicated blocks endpoint documented here — Explorer's read surface is address- and transaction-first. If your use case genuinely needs raw block data, reach for a Dogecoin node RPC directly rather than routing it through Explorer.

Quantum / PQC registry

Explorer also carries a set of post-quantum-signature registry endpoints under /api/pqc/*, part of the ecosystem's forward-looking Falcon-signature attestation work described in the security model. Most integrations won't need these directly.