← previous blocknext block →recent activity
Analyzing
Block #88,366,719
20 transactions · 18 stateful · 2026-07-17 14:50:17 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,366,719 · 20 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
1w02w13w24w37w08w110w115w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefb26182…d522
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x17ca7036…1e16
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0xefb2618287…4cd522
Audit this contract →
← previous block·next block →recent activity