# SwissDLT Explorer: full reference URL: https://explorer.swissdlt.tech/ Summary: https://explorer.swissdlt.tech/llms.txt Network website: https://swissdlt.tech/ Provided by Operal AG (https://operal.biz), a member of the Association of SwissDLT Node Operators. ## 1. What it is The SwissDLT Explorer is a lightweight, read-only block explorer and network dashboard for SwissDLT, chain ID 94. It is a static site with no runtime backend: no database, no wallet connection, no API key, no private key, no transaction signing and no serverless function. The browser reads chain data directly from the two public JSON-RPC endpoints and compares them. Nothing in the explorer signs or sends transactions. It is not a full Blockscout replacement. It does not provide complete address history, token-holder indexes, internal transactions or verified-contract source. ## 2. Network facts - Chain ID: 94 (0x5e) - Client and consensus: go-ethereum, Clique proof of authority; six signers seal a block every four seconds - EVM level: Berlin; legacy (type 0) transactions, gas price 1 gwei, no EIP-1559 base fee - Native coin: BCTS, 18 decimals - Genesis block hash: 0x4a645a22b8540f57400bad6db13a0866f5a7e612e42b39d5be24fe60aebf4151 - Current network since: block 1, 07:11:34 UTC on 18 May 2023 - Public RPC: https://rpc.swissdlt.ch and https://rpc2.swissdlt.ch (JSON-RPC over HTTPS POST, no key) - WebSocket: wss://rpc.swissdlt.ch/ws - Signer set, operators and parameters: https://swissdlt.tech/network.html - Status and incidents: https://swissdlt.tech/status.html In a Clique block the coinbase/miner field carries signer votes, not the block producer. The explorer shows that field as "Clique vote" and does not claim it identifies the sealer. ## 3. Views and routes Routes live in the URL fragment and are rendered by JavaScript in the browser. - / (no fragment): network dashboard. Two views, chosen with "View" and stored in localStorage under swissdlt.explorer.style (default "bi"): - Intelligence view: canonical head, head age, RPC health score, block cadence against the four-second target, empty versus transaction-carrying blocks, GOG activity pattern (area, bar or heatmap), counterparty concentration, index synchronisation, latest GOG events, recent blocks; snapshot JSON download, print, CSV export - Classic view: latest block, head age, gas price, RPC peer count and client version, canonical-hash comparison of both RPCs, ten most recent blocks - #/block/: block hash, parent hash, timestamp (UTC), transaction count, gas used and limit, size, total difficulty, Clique vote field, extra data, first 50 transactions, raw RPC result - #/tx/<0x 64-hex hash>: transaction hash, status from the receipt, block, from, to, contract address, value in BCTS, nonce, gas limit, gas price, gas used, event-log count, input data, raw RPC result. A 66-character hash is checked as a transaction first; if none matches, it is looked up as a block hash. - #/address/<0x 40-hex address>: BCTS balance, transaction nonce, deployed code size, address type, and balanceOf() on the reference tokens (Wrapped BCTS (A), Wrapped BCTS (B), GOG). Complete address history needs an indexer and is out of scope. - #/app/gog: GOG voucher activity (acrevis / Gossau). Filters by text, event type (transfer, mint, burn) and period (24 hours, 7 days, 30 days, all indexed); metrics; 14-day chart; "Check latest on-chain" reads new Transfer logs since the last indexed block; CSV export; optional browser alerts. - #/app/urstamm: Urstamm candidate registry with search by serial, lot or contract address. - #/certificate/<0x contract address>: product passport view: registry evidence, contract code size, name, symbol, reported supply, registered document hash, public verification link, local SHA-256 file check, QR code for the verification link. Search entry point: https://explorer.swissdlt.tech/?q= forwards to the matching route. A decimal number opens a block, a 0x hash with 64 hex characters opens a transaction, a 0x address with 40 hex characters opens an address. ## 4. RPC methods the explorer calls eth_blockNumber, eth_getBlockByNumber, eth_getBlockByHash, eth_getTransactionByHash, eth_getTransactionReceipt, eth_getBalance, eth_getTransactionCount, eth_getCode, eth_call (balanceOf, name, symbol, totalSupply), eth_getLogs (GOG Transfer events), eth_gasPrice, net_peerCount, web3_clientVersion, eth_syncing. Routing between endpoints: automatic failover (default), RPC 1 only or RPC 2 only. Every minute both endpoints report their head; the explorer fetches the block at the lower of the two heads from each and compares the hashes ("Match", "Divergence" or "Partial"). ## 5. Data files Base URL: https://explorer.swissdlt.tech All files under /data/ allow cross-origin reads (Access-Control-Allow-Origin: *) and are cached for five minutes. A scheduled GitHub Action runs the indexer every hour at minute 17 and commits updated files; the site redeploys from that commit. ### /data/gog.json GOG Transfer index for the token 0x43cf6bfb19422e5a9ae2a411929f7e48d7e7106f (18 decimals). Top-level fields: schemaVersion, chainId (94), application, token {name, address, decimals}, generatedAt (ISO time), coverageStart (first indexed block), lastIndexedBlock, completeThrough, eventCount, newEventCount, blockTimes {block number: unix seconds}, events []. Each event: blockNumber, blockHash, transactionHash, logIndex, from, to, value (raw integer string, 18 decimals), timestamp (unix seconds). Event identity is transactionHash:logIndex. Convert values to GOG units only for display; they are not BCTS or fiat amounts. The index is not a full-history index: its authoritative coverage is coverageStart to lastIndexedBlock. ### /data/gog-feed.xml Atom feed of the latest 25 GOG events. Each entry links to the transaction in the explorer. ### /data/urstamm-registry.json Fields: schemaVersion, application, updatedAt, registryStatus ("unofficial_candidates"), notice, identity {name, ens, address, verified, relation}, entries [] with id, name, address, status, documentHash, events, note. The entries are research candidates, not an official Urstamm contract registry. Certificate authenticity and issuer mapping require confirmation from Urstamm or the association. ## 6. Reference contracts Verify against the canonical registry before integrating; the full list is at https://swissdlt.tech/docs.html#contracts. - Wrapped BCTS (A): 0x4C9204BE7d41E8b1d0f8025A60110d866C0574Ad. The wrapped BCTS that SwissDLT Swap and Token Studio use (their deployment.json and contracts.json name it as wrappedNative). - Wrapped BCTS (B): 0x0937f6d21Ee71d1F72127cFDC28B2D17af21cba2. Second wBCTS deployment; canonical status pending the association's registry. Two versions exist; check which one the canonical registry names before integrating. - GOG: 0x43cf6bfb19422e5a9ae2a411929f7e48d7e7106f. Recurring voucher-like activity observed on chain. Issuer documentation should be confirmed. - ChainBridge: 0xDac6e138939459ccB3a150419D408Dccd8a01Ffe. Self-hosted bridge contract. Relayer status and UI availability are separate operational concerns. - Urstamm identity: 0x000000f242305fe32a45d0b5dfa5b87d584de611 (urstamm.eth). ENS-linked DAO membership identity; not an application contract. ## 7. Evidence and limits - GOG activity measures the voucher token contract. It is not a count of acrevis customers, merchants, redemptions or fiat turnover. - Address frequency is not identity evidence. Do not infer wallet owners or locations from transaction patterns. - Urstamm entries are unverified research candidates, not an official issuer registry. urstamm.eth verifies an ENS-linked DAO identity, not an application contract. - Certificate files are hashed locally in the browser and never uploaded. A computed hash alone proves nothing until an official reference hash is registered. SHA-256 proves only that two document fingerprints match; it does not prove issuer identity. - A QR link opens a registry or certificate view; it does not authenticate an issuer. - Complete address history, token-holder indexes, internal transactions, source-code verification and a full Blockscout database are out of scope. - RPC health and consensus agreement are point-in-time observations and may change. ## 8. Documentation - Quickstart, add SwissDLT to a wallet: https://swissdlt.tech/docs.html#quickstart - Contracts: https://swissdlt.tech/docs.html#contracts - Assets: https://swissdlt.tech/docs.html#assets - APIs and RPC: https://swissdlt.tech/docs.html#apis - Run a node: https://swissdlt.tech/docs.html#nodes - FAQ: https://swissdlt.tech/docs.html#faq - Network documentation on GitBook: https://bcts-1.gitbook.io/swissdlt/ ## 9. Machine-readable files and Thirdfy package - /.well-known/contracts.json: chain 94, every address the Explorer reads (GOG token, Urstamm identity, Urstamm candidates, Wrapped BCTS (A) and (B), ChainBridge) with explorer link, kind, observed code size, the code or data file it comes from, and the ABI URL. Deployment blocks and transactions are not recorded in this repository and are given as null. - /.well-known/abis/erc20-minimal.json: the minimal ERC-20 interface the Explorer calls (balanceOf, name, symbol, totalSupply) and the Transfer event. Not a verified source artifact. - /thirdfy-app.json (mirror: /.well-known/thirdfy-app.json): Thirdfy app manifest. appId swissdlt_explorer, kind data, category flows, upstream transport rest at https://explorer.swissdlt.tech with no auth. Two read actions, both GET of a fixed path with no params and billing tier read_offchain: get_swissdlt_gog_activity (/data/gog.json) and get_swissdlt_urstamm_registry (/data/urstamm-registry.json). The whole JSON reply is the reading. The Atom feed is XML and is not an action. - /.well-known/thirdfy-readiness.json: status "prepared-for-submission". Not submitted, listed or certified. The official Thirdfy JSON Schema URL returned HTTP 404 when checked, so only published-reference checks and real HTTPS fixtures have been run. The Explorer has no MCP endpoint; a read-only Explorer MCP is a backlog item. There are no write actions. - Source package: integrations/thirdfy/ (generator, probe, observations, README). ## 10. Other SwissDLT services - Swap: https://swap.swissdlt.tech - Token Studio: https://studio.swissdlt.tech - Bridge: https://bridge.swissdlt.tech - SwissProof: https://timestamp.swissdlt.tech - Oracle: https://oracle.swissdlt.tech (provided by Operal AG)