← previous blocknext block →recent activity
Analyzing
Block #86,297,883
28 transactions · 23 stateful · 2026-07-08 00:13:12 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,297,883 · 28 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
1w02w13w24w35w18w29w310w420w421w422w323w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6e8303…1df1
0xd32edf…ff58
9 touches
10 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
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
10 conflicts on slot 0x5b6e830398…471df1
Audit this contract →
← previous block·next block →recent activity