← previous blocknext block →recent activity
Analyzing
Block #111,064,932
24 transactions · 21 stateful · 2026-10-06 14:43:59 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,064,932 · 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
4w012w013w015w116w117w119w020w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ea2b33b…7dbc
0x508254…98bd
6 touches
3 conflicts
0x29104487…7b9b
0x508254…98bd
6 touches
3 conflicts
0xe0bfc6c5…de37
0x508254…98bd
4 touches
1 conflict
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x8c49c85c…ee96
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: 0x508254c8…4a98bd
3 conflicts on slot 0x4ea2b33b1b…857dbc
Audit this contract →
← previous block·next block →recent activity