Network

Explorer Guide

A block explorer where every panel knows the slot it was read at.

The Pluid explorer is the human face of the read mesh. Every view is backed by the same receipt-bearing API the SDK uses, so what you see on screen is verifiably fresh — the slot anchor travels with the data.

The search bar classifies your input and routes you to the right view. It accepts:

  • Addresses — wallets and program accounts.
  • Mints — resolved to the token view with supply and holders.
  • Signatures — opened as a transaction.
  • Slots — opened as a block.
  • .sol domains — resolved to their owning address.

The same resolution is available programmatically at /api/v1/search.

Accounts

An account view shows the SOL balance, parsed account info, token holdings, and recent activity. Holdings and history come from the portfolio and history routes; balances carry the slot they were read at.

Tokens

The token view surfaces supply, decimals, and metadata, plus a paginated holders table. Large addresses are truncated head…tail with copy-to-clipboard throughout.

Blocks & Transactions

Open any slot to inspect its block — blockhash, parent, timestamp, and transaction summary. Open any signature for full transaction detail; request the enhanced view for a parsed, human-readable breakdown, and use Explain for a one-line plain-English summary.

Live Header

The global stats strip is driven by the realtime stream — slot, TPS, epoch progress, and priority fee update continuously with a live indicator.

Same data, two doors
Anything you can see in the explorer you can fetch from the REST API with a verifiable receipt. The explorer is a convenience layer over an open, provable read mesh.