← previous blocknext block →recent activity
Analyzing
Block #89,581,153
23 transactions · 22 stateful · 2026-07-23 06:10:13 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,581,153 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w010w011w112w213w214w316w317w018w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x260cdf5e…dbbb
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x81dbafca…d1ea
0x851145…3f07
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb1526c23…f2b6
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
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
6 conflicts on slot 0x260cdf5e09…90dbbb
Audit this contract →
← previous block·next block →recent activity