← previous blocknext block →recent activity
Analyzing
Block #86,715,260
16 transactions · 11 stateful · 2026-07-09 22:44:37 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,715,260 · 16 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
1w02w13w25w37w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x145b9bbf…e50e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x97db5885…b42e
0x34b655…2a6f
6 touches
3 conflicts
0x145b9bbf…e50f
0x34b655…2a6f
6 touches
3 conflicts
0xa89ac109…fedd
0xd32edf…ff58
5 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x145b9bbfee…a5e50e
Audit this contract →
← previous block·next block →recent activity