← previous blocknext block →recent activity
Analyzing
Block #86,961,594
35 transactions · 30 stateful · 2026-07-11 02:11:00 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,961,594 · 35 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
1w02w13w15w26w27w08w112w013w114w216w217w318w419w529w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x353033e8…f127
0xd32edf…ff58
11 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x44d7acbf…e680
0x1b6862…e19c
6 touches
3 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 0x353033e873…4ef127
Audit this contract →
← previous block·next block →recent activity