← previous blocknext block →recent activity
Analyzing
Block #86,767,723
25 transactions · 20 stateful · 2026-07-10 04:35:12 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,767,723 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w110w011w112w215w218w320w423w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eeb2a30…6909
0x34b655…2a6f
8 touches
6 conflicts
0x3a6290da…e683
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x868cc668…a119
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0x9f71c3a3…ffc9
0x34b655…2a6f
4 touches
1 conflict
0xab6631d8…b3de
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x0eeb2a3089…8a6909
Audit this contract →
← previous block·next block →recent activity