← previous blocknext block →recent activity
Analyzing
Block #85,173,134
20 transactions · 17 stateful · 2026-07-02 19:15:30 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,173,134 · 20 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
2w03w14w25w17w29w010w311w312w115w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff152553…2367
0xd32edf…ff58
7 touches
6 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x8a2f9a36…fb4a
0xfa32f9…f3f0
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xdc95131b…ae64
0x34b655…2a6f
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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
6 conflicts on slot 0xff152553aa…d92367
Audit this contract →
← previous block·next block →recent activity