← previous blocknext block →recent activity
Analyzing
Block #106,430,050
21 transactions · 20 stateful · 2026-09-20 09:41:24 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,430,050 · 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
2w03w14w05w18w09w110w211w112w313w414w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3867819…9d3c
0x34b655…2a6f
12 touches
15 conflicts
0x987964a7…fdce
0x34b655…2a6f
8 touches
6 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0x8d175439…fb79
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x7cc83eb6…dda1
0x34b655…2a6f
4 touches
1 conflict
0x8e7695d2…21ed
0x34b655…2a6f
4 touches
1 conflict
0xc8cb0701…3926
0x34b655…2a6f
4 touches
1 conflict
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 0xf3867819cd…5a9d3c
Audit this contract →
← previous block·next block →recent activity