XPF Chain Explorer
A technical view into block headers, supply metrics, and node status. All live data is retrieved directly from your local node via JSON-RPC.
This explorer presents a minimal, privacy-conscious interface for observing the Layer-1 chain. It displays only consensus-visible information and performs no tracking, analytics, or address profiling.
Block/transaction tables below currently display mock data until the backend parser is completed. The Network Overview section at the top is fully live.
Search
Block, transaction, and address lookups will be available once the backend indexer is implemented. The current search bar is a placeholder.
The “Network overview” panel displays live information retrieved from your node using
get_sync_status. This includes height, supply information, tip age, and sync state.
Network overview (live)
Waiting for node…
Powered by get_sync_status.
Mempool snapshot (mock)
This is placeholder data. Live mempool inspection will be enabled once RPC pagination is added.
Recent blocks (mock)
These block entries illustrate the final layout. The table uses mock values until the explorer backend is connected.
| Height | Block hash | Time | Tx | Reward | Winner |
|---|---|---|---|---|---|
| #12,345 | 00000b1c...92af | 27s ago | 9 | 1.00000000 XPF | XPF1q...9k3 |
| #12,344 | 00000a98...77cd | 6m 29s ago | 7 | 1.00000000 XPF | XPF1q...4zv |
Recent transactions (mock)
Transaction display will be connected to live chain data once block parsing is implemented. The current protocol supports transparent transfers only.
| Tx ID | Type | Block | Time | Fee |
|---|---|---|---|---|
| tx1a3f...92bc | Transparent | #12,345 | 25s ago | 0.001 XPF |
Block & transaction detail (preview)
Example layouts for block and transaction detail pages. These values are mock placeholders.
Block detail (example)
Transaction detail (example)
Privacy philosophy
The explorer reflects only transparent consensus-visible data. No address clustering, labeling, fingerprinting, or analytics occur. The current protocol does not include shielded transactions.
- No tracking or analytics scripts
- No deanonymization tools
- No user profiling
- No inference based on address activity
Any future privacy extensions will be optional and implemented as separate higher-layer modules, not changes to core consensus.