← previous blocknext block →recent activity
Analyzing
Block #86,989,064
18 transactions · 18 stateful · 2026-07-11 05:14:33 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,989,064 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w010w112w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7e1952…d9c9
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x31c77e11…2fd8
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0x666b28db…11f0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xfc579304…92c2
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
3 conflicts on slot 0x6c7e195218…27d9c9
Audit this contract →
← previous block·next block →recent activity