Native Platform Explorer

What this is

A client-only block explorer for Dash Platform, powered exclusively by @dashevo/evo-sdk v4.0.0-rc.2. There is no API server, no database, and no indexer behind this site — every value you see has been fetched from a masternode's DAPI endpoint by the WASM SDK running in your browser, and (by default) verified against a prefetched set of quorum public keys.

It is a deliberate, reduced-scope sibling of platform-explorer. Because it has no indexer it cannot browse every identity, contract, token, block, or transaction. In exchange, it can ship as a single static bundle that anyone can host, every response carries a cryptographic proof, and there is no middleman between you and the network.

Proofs

Your browser connects directly to DAPI and asks for data. In trusted mode the SDK also asks DAPI for a GroveDB Merkle proof; the WASM engine then verifies that proof locally against quorum public keys fetched when the SDK connected. The UI surfaces the outcome via the ProofChip next to each DigestCard.

Some SDK methods (system status, quorum info, DASH/USD rate, a few boolean DPNS helpers) have no proof variant — we label those honestly as "No proof", rather than pretending otherwise.

Enumeration

Dash Platform's SDK does not expose "list all identities", "list all contracts", "list all tokens", "list all documents", or "list all transactions" primitives. This explorer honours that constraint — wherever you'd expect a browseable list, we either show a seeded list (paste the IDs you care about) or, where the SDK has a real list primitive (documents within a contract, epochs by index, DPNS labels by prefix, protocol votes, contested resources, groups in a contract), we show a real, paginated browser.

The raw GroveDB read that would fix this — system.pathElements, which the explorer exposes on the Tools page — is a KeysInPath batched point-get, not a range scan. You must already know the keys you want; there is no subtree enumeration exposed in @dashevo/wasm-sdk today. Full findings are in docs/research/2026-04-22-path-query-and-token-lookup.md.

One real win in the same family: looking up a token by its ID alone now works. The SDK's tokens.contractInfo(tokenId) hits the GroveDB reverse index at [RootTree::Tokens, TOKEN_CONTRACT_INFO_KEY] and returns the owning contract + token position, so /token/?id=… resolves name, decimals, supply limits, and every token rule from the token ID without any prior context.

Privacy

Your queries go directly from your browser to DAPI. We never see them. No analytics, no telemetry. The session-viewed-identities log (opt-in) is stored only in your browser's localStorage and never transmitted.

Credits

Built on top of dashevo/platform, @dashevo/evo-sdk, and visually mirrors pshenmic/platform-explorer.