← previous blocknext block →recent activity
Analyzing
Block #85,713,450
24 transactions · 23 stateful · 2026-07-05 07:15:08 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,713,450 · 24 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
1w02w13w24w35w47w08w112w013w115w016w117w219w220w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2644aca…40d3
0xd32edf…ff58
7 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xac33ff75…077b
0xfa32f9…f3f0
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 0xd2644acafd…4f40d3
Audit this contract →
← previous block·next block →recent activity