← previous blocknext block →recent activity
Analyzing
Block #106,420,219
22 transactions · 21 stateful · 2026-09-20 08:51:56 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,420,219 · 22 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
1w02w03w18w19w011w112w213w214w315w416w517w618w721w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x781f916d…2a05
0x34b655…2a6f
16 touches
28 conflicts
0x2c2761c0…476e
0x34b655…2a6f
10 touches
10 conflicts
0x5d1ac445…5233
0x34b655…2a6f
10 touches
10 conflicts
0xebf19faa…72cb
0x34b655…2a6f
10 touches
10 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0xfb1d5846…56af
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
28 conflicts on slot 0x781f916d28…b52a05
Audit this contract →
← previous block·next block →recent activity