← previous blocknext block →recent activity
Analyzing
Block #85,983,159
23 transactions · 19 stateful · 2026-07-06 13:12:00 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,983,159 · 23 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
1w02w13w24w35w48w09w114w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79ac7888…c60f
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08115cd3…ed2c
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
0x00000000…001a
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
15 conflicts on slot 0x79ac788881…4ac60f
Audit this contract →
← previous block·next block →recent activity