← previous blocknext block →recent activity
Analyzing
Block #74,183,567
17 transactions · 14 stateful · 2026-05-12 21:19:05 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,183,567 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w411w012w413w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d334689…067f
0xd32edf…ff58
9 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0xeea3f128…72db
0x34b655…2a6f
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
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 0x0d33468919…dc067f
Audit this contract →
← previous block·next block →recent activity