← previous blocknext block →recent activity
Analyzing
Block #86,657,660
16 transactions · 15 stateful · 2026-07-09 16:20:14 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,657,660 · 16 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
1w02w15w06w17w28w29w310w412w314w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xa9f59232…f58c
0x34b655…2a6f
6 touches
3 conflicts
0x671703d0…94b1
0x34b655…2a6f
4 touches
1 conflict
0x72880226…1435
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
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
15 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity