← previous blocknext block →recent activity
Analyzing
Block #95,724,686
20 transactions · 17 stateful · 2026-08-13 20:19:31 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,724,686 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w210w311w412w013w114w216w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x180fcaee…5500
0x34b655…2a6f
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x198be7b6…7132
0x065c9d…c394
6 touches
3 conflicts
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x7f63a266…68c0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0x180fcaee20…b45500
Audit this contract →
← previous block·next block →recent activity