Explorers teach users (and you) how the chain looks. Build a focused UI over regtest or an Esplora-compatible API.
Complete Step 1 // Required reading in the study plan above, then continue here.
Step 2 — Goal
Create pages for:
- Recent blocks
- Transaction detail (vin/vout, fee, weight)
- Address summary (funded txouts)
Optional: pending mempool list or simple fee histogram.
Loading diagram…
Done when: You can sketch the three primary routes and their data sources.
Step 3 — Milestones
| Phase | Ship |
|---|---|
| Milestone A | Block list + block detail from Core/Esplora |
| Milestone B | Transaction and address views with loading/empty/error states |
| Milestone C | Mempool pending list or fee snapshot |
Done when: Milestone A is usable before you polish charts.
Step 4 — Build & evidence (lab)
Implement against /projects/block-explorer. Capture repo link, UI proof, and one failure case.
Common mistakes
- Blocking the UI thread on full-chain scans
- Showing raw RPC errors to end users
- Assuming mempool views are identical across peers
Done when: Lab evidence is filed.
Next lesson
Node Dashboard — peers, sync, and fee estimates as live ops signals.