← previous blocknext block →recent activity
Analyzing
Block #105,841,956
22 transactions · 22 stateful · 2026-09-18 08:20:27 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,841,956 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w07w08w112w113w216w117w218w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0xf103301b…c5cb
0x34b655…2a6f
8 touches
6 conflicts
0xf7ba1e5d…b56b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
6 conflicts on slot 0xc10b903def…412f54
Audit this contract →
← previous block·next block →recent activity