← previous blocknext block →recent activity
Analyzing
Block #111,060,542
24 transactions · 21 stateful · 2026-10-06 14:21:51 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,060,542 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w09w115w216w217w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x12337b6a…2beb
0x34b655…2a6f
4 touches
1 conflict
0x2290912b…2613
0x34b655…2a6f
4 touches
1 conflict
0x34b92998…c975
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity