Native Platform Explorer
What this is
A client-only block explorer for Dash Platform, powered exclusively by @dashevo/evo-sdk v5.0.0-rc.8. There is no API server, no database, and no indexer behind this site — network data is fetched from a masternode's DAPI endpoint by the WASM SDK running in your browser. Proof-capable responses are always verified against prefetched 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 and verify proof-capable responses locally. Quorum public keys are supplied by a trusted service.
Proofs
Your browser connects directly to DAPI and asks for data. 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 browser trusts that service for those keys and does not independently validate Dash Core consensus. The proof controls show the SDK's verification outcome separately from whether proof bytes were captured. Ordinary trusted SDK calls can verify internally without returning those bytes.
Some reads have no proof: system status, the quorum list (the SDK infers each quorum's type and threshold from its member count, and the explorer marks them as inferred), state-transition results, DPNS name resolution and availability (dpns.resolveName, dpns.isNameAvailable), the local DPNS name checks, and the DASH/USD rate from Coinbase. Those are labeled "No proof". Network and query errors are shown as unavailable; only explicit proof verification errors are labeled as failed verification.
Open a proof control or the Query Inspector to see the query's original retrieval time, network, response height when returned, and quorum-key source. Export evidence JSON to save that response and any captured proof bytes. The file records the observed SDK outcome; it is unsigned, has not been independently verified, and does not establish that the response is still current.
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, evonode block counts, contested resources, groups in a contract), we show a real, paginated browser.
Platform also caps some lists. Contract and document history return at most 10 entries per request, and contract history has no offset, so only the 10 newest contract versions can be shown. History exists only for contracts and document types that keep it. Shielded notes load in windows of 8,192. Token holders are only the identities you supply, because there is no holder index.
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.
Write mode
Opt-in, and off in read-only deployments. Every operation is built, reviewed (inputs that contain private keys are never shown back), signed, and broadcast from your browser; mainnet needs a typed confirmation. Contract, document, token, DPNS and most identity operations sign with the identity connected on the wallet page, from a bridge backup, a mnemonic or a single WIF key, and only with an enabled on-chain key of the purpose and security level Platform requires. The browser-extension option only detects the extension; it cannot sign yet. Platform address operations (except funding addresses from your identity), asset-lock identity creation and top-ups, and masternode votes take their keys in the form instead and keep them in the tab only for that operation. The explorer does not build asset-lock transactions: bring the proof from a Core wallet, or use the bridge.
Keys are never saved. A connected signer is cleared when you disconnect, after ten minutes without input, when you leave the wallet and broadcast pages, and when the tab closes; only the signer type and public identity ID are kept for this tab as a reconnect hint. Byte arrays the explorer owns are zeroed, but JavaScript strings and copies inside the SDK cannot be reliably erased. Writes are refused while the SDK session and the network run different Platform protocol versions.
If a write fails after it was sent, the outcome is reported as unknown: check the affected identity or address before you send anything again, because a retry may spend twice. A signed transition from another tool can be decoded and broadcast unchanged under Advanced.
Privacy
Your queries go directly from your browser to DAPI. We never see them. No analytics, no telemetry. Your browser also contacts the network's quorum service (for quorum keys and the masternode list), Dash's Insight API or a custom devnet's own Insight URL (for the Core block height), the DASH/USD rate provider (Coinbase by default, unless the deployment turns it off), a remote well-known registry if the deployment configures one, and the bridge only if you follow a bridge link.
Settings, saved items, saved queries, local registry entries and custom devnets are stored only in your browser's localStorage. The viewed-identities log is opt-in and stored the same way. None of it is transmitted.
For mainnet and testnet, the SDK also keeps up to 100 data contracts it has fetched (dash-sdk.contracts.<network>) and the network's protocol version (dash-sdk.protocol-version.<network>) in localStorage, so later visits load faster. These hold public Platform data only, nothing about you or your keys. You can clear them from Settings → Connection.
Verify this build
This site was built from commit 542395e8103e. Every deployment publishes integrity.json: the SHA-256 of every file it serves, plus the commit, build settings and toolchain. Builds are reproducible, so anyone can rebuild that commit and check that the server sends exactly the files the public source produces:
git clone https://github.com/PastaPastaPasta/native-platform-explorer
cd native-platform-explorer
git checkout 542395e8103ea79250ef94b1eb4d368c42d2aff6
pnpm install --frozen-lockfile
NEXT_PUBLIC_BRIDGE_URL=https://bridge.dashhq.org pnpm build
pnpm verify:integrity <this site>/- Build with the
NEXT_PUBLIC_*values the deployedintegrity.jsonlists underenv(the command above matches this site's production build), on Linux with Node 22 and the pnpm version pinned inpackage.json. verify:integritycompares yourout/integrity.jsonwith the deployed one, then downloads every file from the site and hashes what the server actually returns. It explains likely causes of a difference, such as another commit or base path.
Each page pins every script it runs: its Content Security Policy lists the SHA-256 of each inline script, every script and stylesheet tag carries a Subresource Integrity hash, and the script loader carries the hash of every chunk it loads later, including the SDK and its WASM, and refuses any file it has no hash for. The proof parser's WASM is fetched with its hash too. So once a page's HTML matches the source, so does the code it executes. The check covers what the server returned to you when you ran it; it does not prove what other visitors receive. Platform data is a separate question, answered by the proofs described above.
After a first visit, a service worker keeps the explorer's files so it opens offline. It only stores files whose hash matches this build, always fetches pages from the network first, and offers a reload when a new version is deployed.
Credits
Built on top of dashevo/platform, @dashevo/evo-sdk. It started as a sibling of pshenmic/platform-explorer.