← previous blocknext block →recent activity
Analyzing
Block #86,978,041
15 transactions · 14 stateful · 2026-07-11 04:00:51 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,978,041 · 15 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
4w05w17w29w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16363afe…d410
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x21683d77…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x80bf58f2…be95
0x34b655…2a6f
6 touches
3 conflicts
0x80bf58f2…be96
0x34b655…2a6f
6 touches
3 conflicts
0x63b98686…0a53
0x34b655…2a6f
4 touches
1 conflict
0x7ad73012…00e2
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 0x16363afee5…28d410
Audit this contract →
← previous block·next block →recent activity