← previous blocknext block →recent activity
Analyzing
Block #86,690,902
20 transactions · 18 stateful · 2026-07-09 20:02:03 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,690,902 · 20 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
1w02w13w24w35w06w17w210w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x4d6dc10f…d525
0xd32edf…ff58
7 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
6 touches
3 conflicts
0xa0a9db0c…d713
0x34b655…2a6f
6 touches
3 conflicts
0xcd81cc7b…8da0
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity