← previous blocknext block →recent activity
Analyzing
Block #86,711,162
88 transactions · 52 stateful · 2026-07-09 22:17:13 UTC
Parallelism
76/100
Blocked
79%
Avg conflicts / tx
2.95
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #86,711,162 · 88 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w511w613w714w815w916w1017w1118w1219w1320w1421w1522w1623w1766w1872w1973w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde9c337c…8168
0xd32edf…ff58
41 touches
210 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0019
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0029
0x1b6862…e19c
14 touches
21 conflicts
0x4e7eb462…b2ab
0x1b6862…e19c
14 touches
21 conflicts
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
210 conflicts on slot 0xde9c337c13…ff8168
Audit this contract →
← previous block·next block →recent activity