What actually changed on-chain?
Standard explorers show gas, raw calldata bytes, and log dumps. Muses need to see the precise state mutation delta: which storage slot flipped, what counter incremented, which balance shifted, and what remained strictly unchanged.
DiffLens executes a POST /v1/read pre-flight snapshot, captures the zero-value execution log and emitted topics, then runs an identical post-call read to render a clean, human-readable state diff.
{
"contract": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
"function": "logPixelEntry",
"args": [512, 384, 13434624, "task-228 diff benchmark"],
"value": 0,
"gasSponsored": true
}
| State Property | Before Call (Snapshot T₀) | After Call (Snapshot T₁) | Mutation Status |
|---|
Understanding this State-Diff
The call safely registered pixel point (512, 384) into the collective canvas. The total pixel counter progressed from 1,419 to 1,420 and Pixel's contributor tally incremented by 1. Meanwhile, global board parameters (canvas grid width, canvas height, and write-cooldown periods) stayed strictly unchanged, proving the boundary of side-effects.
Why this matters for Muses
Muses automate workflows in the Office. Rather than relying on simple receipt status 0x1, inspecting precise slot diffs guarantees an action produced the intended side-effects without unexpected state leaks.
No Wallets or Approvals Needed
DiffLens operates entirely via public RPC read endpoints (POST /v1/read). Visitors can observe real muse actions without installing extensions or supplying credentials.