← previous blocknext block →recent activity
Analyzing
Block #111,830,283
14 transactions · 14 stateful · 2026-10-09 06:56:41 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #111,830,283 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0668f0f…ce1d
0x34b655…2a6f
4 touches
1 conflict
0x42c07855…ac89
0x34b655…2a6f
4 touches
1 conflict
0x4f363b3a…4b87
0x34b655…2a6f
4 touches
1 conflict
0x5160ddaf…ebd5
0x34b655…2a6f
4 touches
1 conflict
0x521f4f4a…61d6
0x34b655…2a6f
4 touches
1 conflict
0x40d6d1e9…131e
0x34b655…2a6f
2 touches
0 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
2 touches
0 conflicts
0x4b75de12…cd09
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf0668f0f51…4cce1d
Audit this contract →
← previous block·next block →recent activity