← previous blocknext block →recent activity
Analyzing
Block #86,788,095
22 transactions · 19 stateful · 2026-07-10 06:51:10 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,788,095 · 22 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
1w02w13w24w35w46w58w013w114w015w616w218w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x756e5858…5384
0xd32edf…ff58
9 touches
10 conflicts
0x91220b8f…7a03
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
10 conflicts on slot 0x756e585812…b75384
Audit this contract →
← previous block·next block →recent activity