Built-in Explorer

Inspect WildRoot directly from the desktop node you run.

WildRoot GUI includes its own Explorer. It reads the node's indexed state directly, distinguishes application Trust from later PoW checkpoint metadata, and avoids making a third-party web service part of the normal user workflow.

Transaction state

See whether a transaction is provisional, community-Trusted, checkpointed and PoW-finalized without collapsing those distinct states into one confirmation number.

Address history

Browse indexed native and EVM activity with cursor-based pagination designed for very large histories.

Contracts & tokens

Inspect contract creation/calls, receipts, logs, token activity and creator-published source from the same local node state.

No external dependency

Your node already has the data needed to explore the chain.

The desktop application links the full node in-process. Its Explorer can consume shared state and indexed projections without requiring a separately hosted public website to be available.

That matters for resilience and verification: users can inspect their own node's view of transactions, wallets, checkpoints and contract state instead of treating a remote web page as authoritative.

WildRoot GUIwallet · node · built-in Explorer · mining controls
Indexed node stateaddresses · Trusted sequence · checkpoints · contracts · tokens
Canonical historynative DAG · EVM receipts/logs · PoW checkpoints
Contract source

Creator-published source is reconstructed from chain history.

A successful contract creator can publish a canonical source bundle through WildRoot's source registry. The GUI Explorer can reconstruct the source files and metadata from accepted chain data rather than relying on an external source-code database.

The interface distinguishes Creator Published source from reproducible bytecode verification. Publisher identity and source integrity are not the same claim as compiler reproducibility.