← previous blocknext block →recent activity
Analyzing
Block #111,829,299
38 transactions · 20 stateful · 2026-10-09 06:51:44 UTC
Parallelism
92/100
Blocked
30%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,829,299 · 38 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
1w06w09w116w020w128w029w130w131w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0xdd6538fb…2b3f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb5c8d13b…49c1
0x34b655…2a6f
6 touches
3 conflicts
0xa65eb531…6e3a
0x34b655…2a6f
6 touches
3 conflicts
0x68af9140…761a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6d8ad688…4bf5
0xa6afd3…d132
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 0x25957369b1…4cc648
Audit this contract →
← previous block·next block →recent activity