← previous blocknext block →recent activity
Analyzing
Block #106,199,255
22 transactions · 21 stateful · 2026-09-19 14:19:50 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,199,255 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w18w19w110w012w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ed92b3f…20ea
0x34b655…2a6f
14 touches
21 conflicts
0x5717771c…45ed
0x34b655…2a6f
12 touches
15 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x3c511739…ebb8
0x34b655…2a6f
6 touches
3 conflicts
0x0de78565…ca08
0x34b655…2a6f
6 touches
3 conflicts
0xf195ad96…e0c3
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
21 conflicts on slot 0x8ed92b3f48…e020ea
Audit this contract →
← previous block·next block →recent activity