Explorer now decodes transaction inputs and events; write check made dry-run

Decoded transaction inputs and event logs are live on explorer.satsuma.one, the public block explorer for Satsuma's chain. A transaction page now shows the named function it called with its arguments, and the events it emitted as named logs, covering both standard events and Satsuma's own. Events the explorer cannot match are shown raw with a note saying so, and the raw hex stays on the page alongside the decoded view.

The same session changed the canary, a recurring check that the chain can still accept transactions, not only produce blocks. "A chain can look perfectly healthy on all of those while nobody can actually transact." "Since Satsuma is permissioned and has little traffic, this is the only signal that the write path works." The check now simulates a zero-value transfer from an operations account every 5 minutes through the chain's public Ethereum JSON-RPC endpoint; nothing is signed, sent or spent. It runs in 0.2 seconds and appears on the status views as a dry-run write-path check. That change is live.

The decision was to stop sending real transactions so that no real funds are used; the earlier version was never funded either. The trade-off is stated plainly: "What it gives up: proof that a real transaction gets included in a block, which only a fee-paying transaction can show."