← previous blocknext block →recent activity
Analyzing
Block #87,132,400
23 transactions · 18 stateful · 2026-07-11 21:12:01 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,132,400 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3ece0a7…7a99
0xd32edf…ff58
15 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x26cdc92a…04ba
0x34b655…2a6f
6 touches
3 conflicts
0x30ab53da…3529
0x34b655…2a6f
4 touches
1 conflict
0x31002ded…ca02
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9f
0x34b655…2a6f
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
28 conflicts on slot 0xc3ece0a788…6a7a99
Audit this contract →
← previous block·next block →recent activity