← previous blocknext block →recent activity
Analyzing
Block #85,853,196
27 transactions · 22 stateful · 2026-07-05 22:45:44 UTC
Parallelism
78/100
Blocked
32%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,853,196 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w014w415w522w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b9c1c2c…bdf2
0xd32edf…ff58
7 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcb4ed39a…7d6d
0x065c9d…c394
4 touches
1 conflict
0xefa6582a…0050
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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
6 conflicts on slot 0x6b9c1c2c54…fcbdf2
Audit this contract →
← previous block·next block →recent activity