← previous blocknext block →recent activity
Analyzing
Block #86,540,515
23 transactions · 21 stateful · 2026-07-09 03:14:22 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,540,515 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w19w210w311w412w517w218w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0xed660153…a905
0x34b655…2a6f
7 touches
6 conflicts
0x2c506459…5351
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a6
0xb1dbf0…c0d3
6 touches
3 conflicts
0x195db46d…a194
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity