floonet explorer

Reference

JSON API

Endpoints

MethodPathReturns
GET/api/summaryEverything on the overview page: tip, stats, algo counts, latest 5 blocks.
GET/api/blocks?before=&limit=Newest-first block list. `limit` max 200, keyset paginated.
GET/api/block/:heightOrHashOne block with its inputs, outputs and kernels.
GET/api/kernel/:excessKernel by excess commitment.
GET/api/output/:commitmentOutput by commitment, including spent status.
GET/api/peersConnected and known peers, straight from the node.
GET/api/mempoolUnconfirmed transaction pool.
GET/api/statusExplorer and indexer health. Useful for monitoring.
GET/eventsServer-Sent Events stream. `tip` on every snapshot, `reorg` on a reorg.

Live updates

Consuming the event stream

const es = new EventSource('https://floo-explorer.btlabs.uk/events');
es.addEventListener('tip', (e) => {
  const s = JSON.parse(e.data);
  console.log(s.chain.nodeHeight, s.latest[0].hash);
});
es.addEventListener('reorg', (e) => console.warn('reorg', JSON.parse(e.data)));

A tip event carries the same object as /api/summary. Events fire on each snapshot rebuild, which happens when a block arrives and every few seconds for peer and mempool changes — so treat it as "current state", not as a per-block log.