← previous blocknext block →recent activity
Analyzing
Block #86,959,993
24 transactions · 23 stateful · 2026-07-11 02:00:18 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,959,993 · 24 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
3w04w15w06w17w28w312w013w114w415w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e9c9ffb…7d7b
0xd32edf…ff58
9 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0xa112f315…1a92
0x34b655…2a6f
6 touches
3 conflicts
0x3684bb9c…2e61
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x48028c31…6829
0x34b655…2a6f
4 touches
1 conflict
0x5571e830…9cea
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x2e9c9ffba8…b67d7b
Audit this contract →
← previous block·next block →recent activity