← previous blocknext block →recent activity
Analyzing
Block #111,072,066
22 transactions · 19 stateful · 2026-10-06 15:20:01 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #111,072,066 · 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
1w02w18w19w210w315w016w117w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa61273…8404
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5de47b2c…de15
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8aeda171…13bf
0x34b655…2a6f
4 touches
1 conflict
0xe807358d…4819
0x34b655…2a6f
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
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
3 conflicts on slot 0xdfa6127337…348404
Audit this contract →
← previous block·next block →recent activity