← previous blocknext block →recent activity
Analyzing
Block #106,471,418
16 transactions · 16 stateful · 2026-09-20 13:09:40 UTC
Parallelism
50/100
Blocked
63%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,471,418 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w410w511w612w713w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c9076e2…4386
0x34b655…2a6f
10 touches
10 conflicts
0x1c840894…764a
0x34b655…2a6f
10 touches
10 conflicts
0xd91d25e4…6a53
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0x4c9076e2e9…a34386
Audit this contract →
← previous block·next block →recent activity