← previous blocknext block →recent activity
Analyzing
Block #111,060,543
23 transactions · 20 stateful · 2026-10-06 14:21:51 UTC
Parallelism
74/100
Blocked
45%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,060,543 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w19w210w311w412w013w114w219w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
12 touches
15 conflicts
0x34b92998…c975
0x34b655…2a6f
10 touches
10 conflicts
0x00456f78…2b80
0x34b655…2a6f
10 touches
10 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
8 touches
6 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x67088d1d…dcd6
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 conflicts
0xfa2527aa…9dd5
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
15 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity