← previous blocknext block →recent activity
Analyzing
Block #111,072,229
16 transactions · 16 stateful · 2026-10-06 15:20:50 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #111,072,229 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x6e0713a8…66c8
0x34b655…2a6f
4 touches
1 conflict
0x082f88b3…c374
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xddf10453…d774
0x34b655…2a6f
4 touches
1 conflict
0xad9eaa9d…0a55
0x34b655…2a6f
4 touches
1 conflict
0xa23619a7…40e4
0x3bd359…433a
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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity