← previous blocknext block →recent activity
Analyzing
Block #85,822,219
11 transactions · 9 stateful · 2026-07-05 19:19:14 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,822,219 · 11 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
1w02w13w24w36w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaf3530c…4f6b
0xd32edf…ff58
7 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xf6009797…7f5b
0x34b655…2a6f
3 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xe069120c…952c
0x000000…012a
2 touches
0 conflicts
0x655ffa9f…64e1
0x065c9d…c394
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
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
6 conflicts on slot 0xcaf3530c10…414f6b
Audit this contract →
← previous block·next block →recent activity