← previous blocknext block →recent activity
Analyzing
Block #111,849,440
16 transactions · 14 stateful · 2026-10-09 08:33:04 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #111,849,440 · 16 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
5w06w07w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab23153…8f44
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0x7a093de7…f590
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x0d8a97d7…b5d8
0x34b655…2a6f
2 touches
0 conflicts
0x132b9de1…183b
0x34b655…2a6f
2 touches
0 conflicts
0x1393df1d…afbd
0x34b655…2a6f
2 touches
0 conflicts
0x70ada9f8…7c6f
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 0x4ab23153bc…fb8f44
Audit this contract →
← previous block·next block →recent activity