← previous blocknext block →recent activity
Analyzing
Block #106,415,642
16 transactions · 16 stateful · 2026-09-20 08:28:53 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,415,642 · 16 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
1w02w13w26w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd41846…1f93
0x6f6493…b480
12 touches
15 conflicts
0x0c728c6d…9f95
0x6f6493…b480
12 touches
15 conflicts
0x107c94b8…ad2b
0x6f6493…b480
12 touches
15 conflicts
0x16e108c9…735d
0x6f6493…b480
12 touches
15 conflicts
0x177b6c15…561c
0x6f6493…b480
12 touches
15 conflicts
0x1a62dab8…1226
0x6f6493…b480
12 touches
15 conflicts
0x213cc235…4340
0x6f6493…b480
12 touches
15 conflicts
0x27cc516b…781e
0x6f6493…b480
12 touches
15 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: 0x6f6493e3…08b480
15 conflicts on slot 0x0bd4184644…a61f93
Audit this contract →
← previous block·next block →recent activity