SWSS Explorer is the public block explorer for SWSS Chain, and it runs on both networks: mainnet at Chain ID 122605 and the testnet at Chain ID 122606. Every deed settlement, every Finality Certificate, every governance proposal and every validator admission is visible in real time, with no intermediary and no SWSS account required. It exists because a settlement layer that asks to be believed about its own settlement volume has not understood what it is for.

What the explorer makes checkable is the substance of the whitepaper rather than a summary of it. A DEED-1 instrument can be traced to the block that settled it; the Finality Certificate attesting that settlement can be read against the batch it belongs to, as described under the Consensus Protocol; and the cumulative supply retired through the Transactional Settlement Levy set out in Tokenomics is a figure anyone can total for themselves rather than a number this document asserts.

It is deliberately independent of the products whose activity it reports. The explorer has its own codebase and its own deployment cycle, so it stays reachable when a product interface is not — which is the property that makes it evidence rather than marketing. The validator set it lists is operated through SWSS NodeX, the deeds it indexes are searchable through the Deed Indexer, and the ecosystem overview lists every product whose settlement appears here.

Both Networks

The same explorer runs against each network, so a contract or an integration can be rehearsed on the testnet and read exactly as it will be read in production. The testnet is a rehearsal of the protocol rather than a reduced version of it — same client build, same block cadence.

What Can Be Verified

Checking A Claim

The last row of that table is the one that matters most, and it is not a convenience. A protocol version published in a document is an assertion; the version a node reports is a fact. In August 2026 those two disagreed across this ecosystem — several properties published a consensus version the running network did not report — and the disagreement was found by asking the network rather than by reading another document. The explorer is where anyone else can ask the same question.

The same applies to every figure this whitepaper states. Product counts, settlement volume, supply retirement and validator uptime are all totals over records the explorer already exposes, which means a reader is never asked to accept a number on the strength of where it is printed. Where a figure here disagrees with the chain, the chain is correct.

Why It Is Counted As A Product

SWSS Explorer was previously counted as part of SWSS Chain, which understated the ecosystem and obscured a distinction that matters: the chain produces the record, and the explorer is the independent means of reading it. They have separate codebases, separate deployment cycles and separate availability characteristics, and the explorer remaining reachable when a product interface is not is precisely the property that makes it useful.