← previous blocknext block →recent activity
Analyzing
Block #85,853,342
25 transactions · 21 stateful · 2026-07-05 22:46:43 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,853,342 · 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
1w02w14w06w07w18w112w015w016w217w318w119w320w121w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85038db4…e4e5
0xd32edf…ff58
7 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x38b5b2ce…c5bb
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
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 0x85038db49e…c2e4e5
Audit this contract →
← previous block·next block →recent activity