← previous blocknext block →recent activity
Analyzing
Block #74,956,238
23 transactions · 17 stateful · 2026-05-16 11:15:21 UTC
Parallelism
70/100
Blocked
59%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,956,238 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w112w213w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ffd064d…ea43
0xd32edf…ff58
13 touches
21 conflicts
0x5b92adc3…3ee9
0x065c9d…c394
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
21 conflicts on slot 0x6ffd064dc0…7fea43
Audit this contract →
← previous block·next block →recent activity