Explorer & indexer¶
DogeSoft’s Explorer is the public face of the indexer—the read model for Dogecoin L1 that the wallet, DRC-20 AMM, and bridge are designed to agree with. That is the point: one source of indexed truth for this ecosystem, not three competing caches.
What you get (human language)¶
- Blocks and time — where anything happened, in height and real-world time.
- Addresses — what the indexer has seen touch an address, with DRC-20 and Doginal (inscription) context where applicable.
- Doginals — inscriptions as first-class objects in the UI, not an afterthought JSON blob.
- DRC-20 — operations and balances the protocol understands, tied to the same read path the swap uses.
- Health — enough status to know the indexer is keeping up with the chain you care about.
- Open HTTP — documented routes for integrators (see API overview); the Explorer is the prettiest client of the same API family.
What makes it “DogeSoft class”¶
| Dimension | What it means |
|---|---|
| Doginals-native | Inscriptions are named, labeled, and routed with the DogeSoft envelope where operators index it—not as generic “unknown blob #412.” |
| DRC-20 in the same breath | Token state and inscription state cohere in the model the AMM and wallet consume. |
| Ecosystem, not a solo toy | Built so Pill and Swap can trust the same UTXO and inscription story you see in the Explorer browser. |
Who it is for¶
- Holders and researchers — read the chain with DogeSoft’s labels and health.
- Marketplaces and builders — integrate against the public API shapes; do not expect this doc to paste production secrets—ever.
- You, at 2 a.m. — when you need to know what that inscription was trying to say.
Next: API overview for the HTTP map, or Inscription standard v1 for byte-level agreement with the indexer parser.