← previous blocknext block →recent activity
Analyzing
Block #111,065,027
14 transactions · 13 stateful · 2026-10-06 14:44:27 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,065,027 · 14 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
2w04w05w16w27w18w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f9b6364…a024
0x34b655…2a6f
4 touches
1 conflict
0x6a46e7d0…6c6c
0x34b655…2a6f
4 touches
1 conflict
0xbb5b533c…7972
0x34b655…2a6f
4 touches
1 conflict
0xcae42d06…49dc
0x34b655…2a6f
4 touches
1 conflict
0xd1b40f29…9b9d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf9f8a78a…25f3
0x34b655…2a6f
4 touches
1 conflict
0x0463db49…5d05
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
1 conflict on slot 0x2f9b6364fc…d7a024
Audit this contract →
← previous block·next block →recent activity