Network facts
Network 94
Read live from the public RPC endpoints, or dated where recorded.
Network 9421:27 UTC
27'322'716Head blockRecorded 21:27 UTC, 7 November 2026
Sealed by reading…
0Transactions in the head block
2 of 2Public RPC endpointsComparing…
Latest blocks
| Block | Time | Sealed by | Tx | Hash |
|---|---|---|---|---|
| Reading the chain… | ||||
The sealer is recovered from each block's Clique signature, in your browser.
Parameters
| Chain ID / network ID | 94 / 94 (0x5e) |
| Client and consensus | go-ethereum, Clique proof of authority; 4-second period, epoch 30'000 blocks |
| EVM level | Berlin; legacy (type 0) transactions, gas price 1 gwei, no EIP-1559 base fee |
| Native currency | BCTS, 18 decimals; 72'000'003 BCTS allocated at genesis; no block reward |
| Current network since | Block 1 at 07:11:34 UTC on 18 May 2023 |
| Genesis hash | 0x4a645a22b8540f57400bad6db13a0866f5a7e612e42b39d5be24fe60aebf4151 |
| Public RPC | https://rpc.swissdlt.ch, https://rpc2.swissdlt.ch; no key required |
| WebSocket | wss://rpc.swissdlt.ch/ws |
| Explorer | explorer.swissdlt.tech (light explorer; the earlier Blockscout instance is offline) |
Signer set
Six addresses seal blocks in turn. The operator behind each key will be named in the operator map.
| Signer | Address | Last block sealed (live) | Operator |
|---|---|---|---|
| Signer 1 | 0xd6bf33d18c9735fb29c31fab4e99ea9711de24c6 | Reading… | Remaining genesis signer; operator to be published |
| Signer 2 | 0xb9861de78c155a01f462c86780965efac034f8fd | Reading… | operator to be published |
| Signer 3 | 0x6553598fe9b2a9fe833310afa5a9b47706d27268 | Reading… | operator to be published |
| Signer 4 | 0xcb10bc239f3f2f66e3dafd49cdb5fdc29a529d1f | Reading… | operator to be published |
| Signer 5 | 0x25b6d134d9bf80e1c7067f6863f93a40d73b9600 | Reading… | operator to be published |
| Signer 6 | 0xf262c129eaa162d307bde38e4baa38c511f2837f | Reading… | operator to be published |
Live, but quiet
Blocks are sealed continuously; application traffic is still sparse. Reports show both.
Next
- Publish the operator map and statutes.
- Add a separate archive and RPC node.
- Agree a client upgrade policy.
- Publish uptime and post-mortems.