← previous blocknext block →recent activity
Analyzing
Block #86,182,287
27 transactions · 22 stateful · 2026-07-07 11:21:19 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,182,287 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w512w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a2061cd…b9f5
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x9fa1409b…0e59
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
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
28 conflicts on slot 0x1a2061cd3f…2bb9f5
Audit this contract →
← previous block·next block →recent activity