← previous blocknext block →recent activity
Analyzing
Block #106,215,299
24 transactions · 21 stateful · 2026-09-19 15:40:38 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,215,299 · 24 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
1w02w13w06w07w18w29w112w313w414w116w517w618w721w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12503a94…ffdb
0x34b655…2a6f
10 touches
10 conflicts
0xda9919d8…4926
0x34b655…2a6f
10 touches
10 conflicts
0xfbabb02d…af07
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x065566a3…cf1b
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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 0x12503a9497…8fffdb
Audit this contract →
← previous block·next block →recent activity