← previous blocknext block →recent activity
Analyzing
Block #85,839,609
25 transactions · 21 stateful · 2026-07-05 21:15:02 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,839,609 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w29w214w015w118w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98fd648a…add5
0xd32edf…ff58
7 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x527f20e3…82e7
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc82e319…b43c
0x5afd3e…7620
4 touches
1 conflict
0xf2e7f9b4…3e26
0x065c9d…c394
3 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
6 conflicts on slot 0x98fd648a35…00add5
Audit this contract →
← previous block·next block →recent activity