← previous blocknext block →recent activity
Analyzing
Block #75,198,960
24 transactions · 14 stateful · 2026-05-17 14:16:25 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,198,960 · 24 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
1w02w13w24w35w413w014w115w216w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc4b59f0…0c7f
0xd32edf…ff58
9 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
6 touches
3 conflicts
0x8b31e1d0…b6d1
0x34b655…2a6f
6 touches
3 conflicts
0xedb848fe…6534
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c1
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
10 conflicts on slot 0xdc4b59f0f6…b20c7f
Audit this contract →
← previous block·next block →recent activity