← previous blocknext block →recent activity
Analyzing
Block #85,201,023
18 transactions · 16 stateful · 2026-07-02 22:21:17 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,201,023 · 18 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
1w02w13w24w38w09w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x660bc583…81ad
0xd32edf…ff58
9 touches
10 conflicts
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x195f0571…eea5
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 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
10 conflicts on slot 0x660bc58390…4281ad
Audit this contract →
← previous block·next block →recent activity