How monetarium/monetarium-explorer works
Monetarium Explorer serves a multi-coin blockchain explorer: a user requests a page or API result, the Go server routes the request to explorer or API handlers, and those handlers use indexed chain data to respond. The broader runtime also collects node data, tracks mempool and governance information, renders charts, and publishes live updates over WebSockets. PostgreSQL is the persistent backend. The graph reflects documented capabilities and indexed imports; unsampled implementation details are not inferred as direct calls.
Main entry points: main.go dcrdata Server · blockdata.go Block Collection · pgblockchain.go PostgreSQL Backend · charts_controller.js Charts View
Components 20
Server Runtime
- dcrdata Server
cmd/dcrdata/main.go
Chain Data
- Block Collection
blockdata/blockdata.go - Node RPC
rpcutils/rpcclient.go - PostgreSQL Backend
db/dcrpg/pgblockchain.go - Chart Cache
db/cache/charts.go - Mempool Monitor
mempool/collector.go - Ticket Tracking
stakedb/stakedb.go
Explorer Features
- Governance Data
gov/agendas/tracker.go
Client Interfaces
- Explorer Pages
cmd/dcrdata/internal/explorer/explorerroutes.go - Explorer API
cmd/dcrdata/internal/api/apiroutes.go - Insight API
cmd/dcrdata/internal/api/insight/apiroutes.go - Live Pub/Sub
pubsub/pubsubhub.go
Browser Experience
- Address View
cmd/dcrdata/public/js/controllers/address_controller.js - Charts View
cmd/dcrdata/public/js/controllers/charts_controller.js - Chart Definitions
cmd/dcrdata/public/js/charts/definitions/address.js - Chart Rendering
cmd/dcrdata/public/js/helpers/chart_panel.js - HTTP Helper
cmd/dcrdata/public/js/helpers/http.js
Other components
- Explorer User
- Monetarium Node
- PostgreSQL
Connections 25
- Explorer User → dcrdata Server: requests pages
- dcrdata Server → Explorer Pages: registers routes
cmd/dcrdata/main.go - dcrdata Server → Explorer API: registers routes
cmd/dcrdata/main.go - dcrdata Server → Insight API: registers routes
cmd/dcrdata/main.go - dcrdata Server → Block Collection: initializes
cmd/dcrdata/main.go - dcrdata Server → Live Pub/Sub: initializes
cmd/dcrdata/main.go - Block Collection → Node RPC: uses RPC
- Node RPC → Monetarium Node: connects to
- Block Collection → PostgreSQL Backend: stores chain data
- PostgreSQL Backend → PostgreSQL: persists data
- PostgreSQL Backend → Chart Cache: updates charts
db/dcrpg/pgblockchain.go - dcrdata Server → Mempool Monitor: starts monitor
cmd/dcrdata/main.go - dcrdata Server → Ticket Tracking: initializes
cmd/dcrdata/main.go - dcrdata Server → Governance Data: initializes
cmd/dcrdata/main.go - Explorer Pages → PostgreSQL Backend: queries chain data
- Explorer API → PostgreSQL Backend: queries chain data
- Explorer API → Chart Cache: checks chart cache
cmd/dcrdata/internal/api/apiroutes.go - Insight API → Block Collection: broadcasts transactions
cmd/dcrdata/internal/api/insight/apiroutes.go - Block Collection → Live Pub/Sub: publishes blocks
pubsub/pubsubhub.go - Explorer User → Address View: opens address
cmd/dcrdata/public/js/controllers/address_controller.js - Address View → HTTP Helper: requests data
cmd/dcrdata/public/js/controllers/address_controller.js - Explorer User → Charts View: selects charts
- Charts View → HTTP Helper: fetches data
cmd/dcrdata/public/js/controllers/charts_controller.js - Charts View → Chart Definitions: gets definitions
cmd/dcrdata/public/js/controllers/charts_controller.js - Charts View → Chart Rendering: renders charts
cmd/dcrdata/public/js/controllers/charts_controller.js