fix: show a block's events, joined to the extrinsics that caused them
deploy / build (push) Successful in 9m18s
deploy / deploy-web (push) Successful in 4s
deploy / deploy-api (push) Successful in 14s

The block page listed extrinsics and nothing else. Block 1 holds twenty-eight
indexed events and the route returned none of them — visible from the outside,
because an account page linked to a `Wormhole::NativeTransferred` at block 1 and
block 1 showed no sign of it.

`phase` and `extrinsic_index` were stored for exactly this join and had never
been used. Each extrinsic now carries its own events beneath it, and the block's
own events sit in their phases.

Block 1 is the argument for doing it that way. As extrinsics alone it is a
single `Timestamp::set`. Its events are the entire opening distribution:
twenty-one `Wormhole::NativeTransferred` in `Initialization`, owned by no
extrinsic at all and sent from the minting account — not block zero, and not
anything a transaction did. `Vesting::LaunchMomentSet` fires there too, so
vesting has been exercised despite the call index showing zero `Vesting::*`
dispatched: a pallet the runtime uses looks unused from the call side alone.

Closes #3

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jp6a8EDar9ueEhAxzep4V5
This commit is contained in:
2026-09-10 09:14:56 +03:00
co-authored by Claude Opus 5
parent dd8086df0d
commit 88086552cb
10 changed files with 337 additions and 6 deletions
+8
View File
@@ -1378,3 +1378,11 @@ tr.mine .share-bar > i {
font-size: 11px;
margin-top: 2px;
}
/* Events nested under the extrinsic that caused them. Indented and quieter
than the call above: they are its consequences, not siblings of it. */
.block-event-list {
margin-top: 6px;
padding-left: 10px;
border-left: 1px solid var(--border);
}