← previous blocknext block →recent activity
Analyzing
Block #106,958,422
22 transactions · 22 stateful · 2026-09-22 06:01:48 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,958,422 · 22 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
2w03w17w211w012w313w314w416w517w018w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60dcfcd4…a1d2
0x34b655…2a6f
12 touches
15 conflicts
0x704a8131…bbe8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
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 0x60dcfcd423…0aa1d2
Audit this contract →
← previous block·next block →recent activity