← previous blocknext block →recent activity
Analyzing
Block #87,704,394
63 transactions · 40 stateful · 2026-07-14 12:58:30 UTC
Parallelism
83/100
Blocked
68%
Avg conflicts / tx
1.56
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,704,394 · 63 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w419w520w621w728w629w730w838w943w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8496f8e8…60bc
0xd32edf…ff58
21 touches
55 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
10 touches
10 conflicts
0x43fab434…896f
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x91220b8f…7a05
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
55 conflicts on slot 0x8496f8e868…e660bc
Audit this contract →
← previous block·next block →recent activity