← previous blocknext block →recent activity
Analyzing
Block #89,403,039
16 transactions · 15 stateful · 2026-07-22 10:20:20 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,403,039 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w110w212w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a366f1e…3909
0xd32edf…ff58
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x584dafa2…f60d
0x34b655…2a6f
4 touches
1 conflict
0x584dafa2…f60e
0x34b655…2a6f
4 touches
1 conflict
0x7c4da3c0…bd23
0x34b655…2a6f
4 touches
1 conflict
0x8f1b3f9a…d537
0x34b655…2a6f
4 touches
1 conflict
0xb6f12e40…9180
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
10 conflicts on slot 0x2a366f1eae…783909
Audit this contract →
← previous block·next block →recent activity