← previous blocknext block →recent activity
Analyzing
Block #86,663,587
19 transactions · 17 stateful · 2026-07-09 16:59:45 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,663,587 · 19 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
4w05w16w27w18w214w315w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15086f36…c164
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x07b979bc…3564
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
6 touches
3 conflicts
0x7f430e47…4cbd
0xb1dbf0…c0d3
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 0x15086f3626…48c164
Audit this contract →
← previous block·next block →recent activity