← previous blocknext block →recent activity
Analyzing
Block #85,172,619
21 transactions · 21 stateful · 2026-07-02 19:12:04 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.62
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,172,619 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w07w18w09w010w112w213w115w216w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4782cc5b…16b5
0xd32edf…ff58
5 touches
3 conflicts
0xcdd6c05b…e79d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb3
0x1b6862…e19c
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
3 conflicts on slot 0x4782cc5be7…d316b5
Audit this contract →
← previous block·next block →recent activity