← previous blocknext block →recent activity
Analyzing
Block #89,666,409
26 transactions · 24 stateful · 2026-07-23 15:24:06 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,666,409 · 26 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
1w02w13w24w35w17w112w013w415w016w118w122w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcacccaf0…7dbd
0xd32edf…ff58
9 touches
10 conflicts
0x03695af7…8944
0x34b655…2a6f
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0x6f95cc9f…e9b5
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8218911e…3bed
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
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 0xcacccaf004…817dbd
Audit this contract →
← previous block·next block →recent activity