← previous blocknext block →recent activity
Analyzing
Block #86,711,178
28 transactions · 21 stateful · 2026-07-09 22:17:19 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,711,178 · 28 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
1w02w03w14w16w07w19w212w314w015w016w119w422w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6a29dd2…a2f5
0xd32edf…ff58
9 touches
10 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xfc578b53…9b1f
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
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 0xb6a29dd29b…fda2f5
Audit this contract →
← previous block·next block →recent activity