← previous blocknext block →recent activity
Analyzing
Block #74,958,884
18 transactions · 15 stateful · 2026-05-16 11:33:10 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,958,884 · 18 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
1w03w14w05w07w28w19w011w212w315w216w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66e80c28…c078
0xd32edf…ff58
7 touches
6 conflicts
0x97ab5017…36a1
0x065c9d…c394
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x3e49348b…9445
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
6 conflicts on slot 0x66e80c28c1…99c078
Audit this contract →
← previous block·next block →recent activity