← previous blocknext block →recent activity
Analyzing
Block #88,365,325
23 transactions · 22 stateful · 2026-07-17 14:40:44 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,365,325 · 23 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
1w03w04w15w07w18w09w110w012w214w119w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2ed336a4…72b1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x46005a44…f34b
0xa6afd3…d132
6 touches
3 conflicts
0x69a491cf…abd7
0xa6afd3…d132
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x8252706a…7ca5
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity