← previous blocknext block →recent activity
Analyzing
Block #75,254,963
13 transactions · 11 stateful · 2026-05-17 20:30:22 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,254,963 · 13 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
1w02w13w24w35w48w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cbf6338…3e6c
0xd32edf…ff58
9 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xfd4a2d49…af1c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
2 touches
0 conflicts
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 0x3cbf633818…ae3e6c
Audit this contract →
← previous block·next block →recent activity