← previous blocknext block →recent activity
Analyzing
Block #106,923,765
38 transactions · 34 stateful · 2026-09-22 03:07:21 UTC
Parallelism
60/100
Blocked
62%
Avg conflicts / tx
2.24
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,923,765 · 38 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w111w012w113w214w315w416w517w618w719w821w122w223w924w1025w1126w1227w1328w1435w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
20 touches
45 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
18 touches
36 conflicts
0x4996be87…663a
0x34b655…2a6f
18 touches
36 conflicts
0xdd460daa…6b5b
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
45 conflicts on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity