← previous blocknext block →recent activity
Analyzing
Block #106,568,250
62 transactions · 42 stateful · 2026-09-20 21:17:00 UTC
Parallelism
74/100
Blocked
71%
Avg conflicts / tx
1.87
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,568,250 · 62 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w010w111w214w016w118w220w322w424w526w627w728w829w938w339w448w749w150w851w952w1053w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x823d27a2…3fd1
0x34b655…2a6f
16 touches
28 conflicts
0xc6615a36…3cf0
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity