← previous blocknext block →recent activity
Analyzing
Block #85,875,244
25 transactions · 18 stateful · 2026-07-06 01:12:25 UTC
Parallelism
80/100
Blocked
61%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,875,244 · 25 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
1w02w13w24w36w28w39w310w011w112w115w016w121w422w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aa8ce4c…3959
0xd32edf…ff58
7 touches
6 conflicts
0xc13fac9b…d2ce
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0003
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
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 0x7aa8ce4ca2…d43959
Audit this contract →
← previous block·next block →recent activity