← previous blocknext block →recent activity
Analyzing
Block #106,924,230
21 transactions · 20 stateful · 2026-09-22 03:09:42 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,924,230 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w29w310w111w212w313w414w518w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
12 touches
15 conflicts
0xbbb93c5b…db1b
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0x6a8d403c…3e46
0x34b655…2a6f
8 touches
6 conflicts
0xd4230a60…bd13
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity