← previous blocknext block →recent activity
Analyzing
Block #85,915,410
25 transactions · 21 stateful · 2026-07-06 05:40:02 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,915,410 · 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
1w02w14w17w28w09w011w113w314w116w018w222w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6619ce0a…51cc
0xd32edf…ff58
7 touches
6 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0x88f26bba…6dd8
0x065c9d…c394
5 touches
3 conflicts
0x1cefae97…7f45
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x321a5566…4d76
0x34b655…2a6f
4 touches
1 conflict
0x14f6fe51…1c24
0x34b655…2a6f
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 0x6619ce0a1e…ac51cc
Audit this contract →
← previous block·next block →recent activity