← previous blocknext block →recent activity
Analyzing
Block #86,660,918
22 transactions · 15 stateful · 2026-07-09 16:41:58 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,660,918 · 22 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
1w02w03w14w05w16w08w19w211w112w313w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87ee379a…cd9e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf4af322a…5856
0x34b655…2a6f
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2878
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2879
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x87ee379aa1…d8cd9e
Audit this contract →
← previous block·next block →recent activity