← previous blocknext block →recent activity
Analyzing
Block #85,930,359
26 transactions · 21 stateful · 2026-07-06 07:19:39 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,930,359 · 26 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
1w02w13w24w35w46w07w18w210w120w021w022w123w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ccfdad0…3da7
0xd32edf…ff58
9 touches
10 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0x1d3dac50…4731
0x34b655…2a6f
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
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 0x5ccfdad0e2…813da7
Audit this contract →
← previous block·next block →recent activity