Skip to main content

Explorer Getting Started

With clutch-deploy​

The explorer is included in the full Docker stack:

git clone https://github.com/clutchprotocol/clutch-deploy.git
cd clutch-deploy
cp .env.example .env
docker compose up -d
ServiceURL
Explorer UIhttp://localhost:5174
Explorer APIhttp://localhost:8088
API healthhttp://localhost:8088/health

Docker images (GHCR only): clutch-explorer-backend, clutch-explorer-frontend. Full list: Docker images.

Standalone development​

See the clutch-explorer repository for backend and frontend setup with Postgres.

Frontend routes​

RoutePage
/Dashboard / stats
/blocksBlock list
/blocks/:idBlock detail
/txsTransaction list
/txs/:hashTransaction detail
/address/:addressAccount page
/validatorsValidator set
/search?q=Search results, when a query matches more than one thing

Press / anywhere to jump to the search box.

Environment variables​

Backend​

Config loads from config/{env}.toml, with environment variables using the APP_ prefix: APP_NODE_WS_URL=ws://... maps to the TOML key node_ws_url, not the bare key name — same rule as the Hub API.

SettingDescription
EXPLORER_POSTGRES_*Database connection (in clutch-deploy .env, composed into APP_DATABASE_URL)
APP_INDEXER_POLL_INTERVAL_MSBlock poll interval (default 4000)
APP_NODE_WS_URLNode WebSocket for indexing
APP_NODE_METRICS_URLNode Prometheus endpoint, read for the chain head (default http://node1:3001/metrics)
APP_TREASURY_PUBLIC_RECONCILIATION_URLThe treasury's /public/reconciliation, republished as /api/v1/reserve. Empty (the default) leaves the reserve section out

Frontend​

VariableDescription
VITE_EXPLORER_API_URLBackend API URL; /api is appended. Default http://localhost:8088 on localhost, otherwise the relative /api. Baked in at build time
VITE_NETWORK_LABELThe network chip in the header. Unset, it is read from the hostname: *-stage.* shows Testnet, *.clutchprotocol.io shows Mainnet pilot, anything else Local

Verify indexing​

  1. Submit a transaction via the demo app or SDK
  2. Wait for the indexer poll (~4 seconds)
  3. Search the transaction hash in the explorer UI or API
curl "http://localhost:8088/api/v1/search?q=0xYourTxHash"