Zolana
ExplorerDocsGitHubOpen wallet

Docs · Use

Explorer

What the explorer shows, why it only covers recent blocks, how its signed feed works, and why it never talks to validators directly.

What it shows

The explorer is a read-only page with recent blocks and transactions from the public devnet.

  • Status row. Network (Live or Paused), tip slot, finalized slot, block height, how many of the validators in the feed are voting, and when the feed was last updated.
  • Recent window. Figures for the blocks in the feed: block time, blocks per minute, transactions, non-vote transactions and skipped slots, with two small charts that have one column per block. The block time is the feed’s average slot time multiplied by the slots per block in the window; it is not measured block by block. Block time, blocks per minute and validators voting are shown only while the network is live. When the feed marks payment-program transactions, a sixth figure, Shielded payments, counts the payments executed in the window’s blocks and says how many payment-program transactions that came from.
  • Latest blocks. Slot, blockhash, age, number of transactions and number of non-vote transactions.
  • Latest transactions. Signature, slot, age, result, fee and kind. The fee column is headed “Fee (test coins)”. The kind is Vote or Program; when the feed marks payment-program transactions it can also be Shielded payment, Payment staging or Payment program, and the list can be limited to those transactions.
  • Search. A slot number, or at least four characters from the start of a blockhash or signature.
  • Details and links. Selecting a block or a transaction opens its details. The page address then ends in #block= and the slot, or #tx= and the signature, and opens the same details again for as long as the item is in the window.

How a shielded payment appears depends on the feed. When the feed does not mark payment-program transactions, a shielded payment appears as an ordinary Program transaction with its signature, slot, result and fee, and the page says so: “The feed does not mark which transactions are shielded payments.” When the feed marks them, a transaction that succeeded and carries the payment program’s finalize or inline instruction is shown as a Shielded payment and counted; the transactions that only stage a payment’s bytes are shown as Payment staging. The mark is the name of an instruction and nothing more: the page says of such a transaction that the feed “does not say whether it was a deposit, a private send or a withdrawal, and it carries no amount”. In both cases the page states: “Private payment amounts and participants are not public.”

The Validators page reads the same feed. It lists each validator in it with its identity, its vote account, its last vote, how many slots that vote is behind the tip slot of the same feed and, while the network is live, whether the feed marks the validator as voting.

Live and Paused

The page shows Live only when the feed reports the network as live and the feed is at most 30 seconds old. Otherwise it shows Paused and keeps the last recorded blocks, with the notice “The network is paused. Showing the last recorded blocks.” While the network is paused the page also gives the reason for the pause and the expected return time.

If the page cannot refresh its data it says so instead: “Explorer data could not be refreshed. Showing the last recorded blocks.”

The recent-window limit

Limit

The explorer covers only a recent window: at most 120 blocks and 200 transactions. There is no deep history, and search only looks inside that window. Full history search is in progress.

Vote transactions are listed only while fewer than 20 non-vote transactions are in the window.

A search that finds nothing says why and ends with “Only the recent window is searchable for now.” For a slot number it says whether the slot is older than the window, ahead of its newest block, or was skipped. For a blockhash or signature it says that nothing in the window starts with those characters. That means the item is not in the window, not that it does not exist on chain.

How the signed feed works

The page never queries a validator. It reads one JSON file from its own origin. That file is produced and moved by two small services in the repository:

  1. The feed service runs next to the validators. It polls a fixed allowlist of read-only RPC methods (getGenesisHash, getSlot, getBlockHeight, getBlocks, getBlock, getVoteAccounts, getHealth) and keeps a rolling window. It writes feed.json and feed.sig, an HMAC-SHA256 signature over the exact bytes of the feed, and serves the two files only to an allowlisted address.
  2. The puller runs on the web host. It fetches both files, checks the signature with the shared key, validates the document strictly against the feed format, and only then publishes the verified bytes with an atomic rename. It never publishes an older feed over a newer one, and any failure leaves the published file untouched.
  3. The page reads the published file every five seconds, validates every value again before use, and shows Live or Paused from the feed’s age.

The feed format is named zolana-explorer-feed-v0. It contains block and transaction metadata only: slots, hashes, times, counts, signatures, results, fees, and for validators an identity, a vote account and a last vote. It carries no transaction contents. The page also reads three things when a feed carries them: for each transaction the names of the payment-program instructions it carries, for each block how many of its transactions carry one and how many executed a payment, and for each validator a root slot. A feed without them is read as before.

Why it never talks to validators directly

  • Validator RPC is not public. The feed exists, in the words of its README, to let “a static web page show recent blocks from the public devnet without exposing validator RPC”.
  • The site forbids it. This site’s content security policy allows scripts and network requests to its own origin only. The page cannot call another host.
  • A small, fixed surface. The feed service can only call the seven read-only methods above. Nothing a visitor types reaches a validator.

What the feed does not prove

The signature protects one hop: it shows the web host received the bytes that the feed service produced. The key is shared between two hosts run by the project, so a visitor cannot check the signature, and it is not a proof of consensus. The explorer is the project’s own view of its network.

Source and tests

The services are in tools/devnet_explorer and the page in clients/devnet-explorer. Their tests run without a network:

cd tools/devnet_explorer
python3 -B -m unittest test_explorer_feed_v0 test_rpc_env
python3 -B test_explorer_pull_v0.py

cd ../../clients/devnet-explorer
node explorer_logic_test.js

Your privacy
has a boundary.

Zolana is an independent blockchain for native shielded deposits, private transfers and withdrawals. The browser wallet creates proofs and decrypts its own notes locally.

Shielded details

Payment amounts and receiving addresses are protected by proofs. Your spending and viewing keys stay on your device.

Public evidence

Blocks, timing, fees, nullifiers and public deposit or withdrawal accounts and amounts remain visible.

The invited gateway knows your membership and receiving address. It sees your IP address and request timing and can link your submissions. This is not a claim of complete anonymity.

Valueless test coins. No Solana bridge, SOL/USDC deposits, post-quantum protection or audited-security claim.