← previous blocknext block →recent activity
Analyzing
Block #111,064,951
23 transactions · 18 stateful · 2026-10-06 14:44:04 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,064,951 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w15w09w210w213w214w315w116w317w419w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0b1d4bb…e250
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xad2d1e03…9a20
0x34b655…2a6f
6 touches
3 conflicts
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x271fb978…841b
0x34b655…2a6f
4 touches
1 conflict
0x5ffebaa2…5d69
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
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
10 conflicts on slot 0xb0b1d4bbbe…9ce250
Audit this contract →
← previous block·next block →recent activity