← previous blocknext block →recent activity
Analyzing
Block #86,084,075
29 transactions · 25 stateful · 2026-07-07 00:25:46 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.97
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,084,075 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w010w011w112w215w418w519w220w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5728054f…f60c
0xd32edf…ff58
11 touches
15 conflicts
0x006ee1d9…5485
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xfa1a8731…ca65
0x34b655…2a6f
4 touches
1 conflict
0xffb8950c…23c6
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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
15 conflicts on slot 0x5728054fe9…5cf60c
Audit this contract →
← previous block·next block →recent activity