← previous blocknext block →recent activity
Analyzing
Block #75,591,347
23 transactions · 21 stateful · 2026-05-19 10:05:17 UTC
Parallelism
57/100
Blocked
67%
Avg conflicts / tx
2.22
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #75,591,347 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w912w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6106daa6…4cc5
0xd32edf…ff58
19 touches
45 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 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
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
45 conflicts on slot 0x6106daa655…464cc5
Audit this contract →
← previous block·next block →recent activity