← previous blocknext block →recent activity
Analyzing
Block #85,570,663
23 transactions · 17 stateful · 2026-07-04 15:22:54 UTC
Parallelism
70/100
Blocked
59%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,570,663 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w110w112w213w216w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62ea14bf…5134
0xd32edf…ff58
13 touches
21 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
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
21 conflicts on slot 0x62ea14bf98…3b5134
Audit this contract →
← previous block·next block →recent activity