← previous blocknext block →recent activity
Analyzing
Block #86,981,580
18 transactions · 17 stateful · 2026-07-11 04:24:32 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,981,580 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w09w511w013w614w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe0d6f36…cff7
0xd32edf…ff58
9 touches
10 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9b334941…fde0
0x1b6862…e19c
4 touches
1 conflict
0x814f0f40…c654
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xfaf3835b…98c7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
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 0xfe0d6f3661…10cff7
Audit this contract →
← previous block·next block →recent activity