← previous blocknext block →recent activity
Analyzing
Block #111,833,016
25 transactions · 25 stateful · 2026-10-09 07:10:26 UTC
Parallelism
76/100
Blocked
20%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,833,016 · 25 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
8w09w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcfccb76…3228
0x34b655…2a6f
12 touches
15 conflicts
0xca608d0c…f23b
0x34b655…2a6f
10 touches
10 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
8 touches
6 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
6 touches
3 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
6 touches
3 conflicts
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
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
15 conflicts on slot 0xbcfccb76b3…633228
Audit this contract →
← previous block·next block →recent activity