← previous blocknext block →recent activity
Analyzing
Block #86,698,638
18 transactions · 17 stateful · 2026-07-09 20:53:39 UTC
Parallelism
61/100
Blocked
35%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,698,638 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w310w411w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x1191dbf7…8e85
0x34b655…2a6f
6 touches
3 conflicts
0x32a1a68b…8ee4
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d8
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d9
0x34b655…2a6f
6 touches
3 conflicts
0x51a9fa57…1dff
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity