← previous blocknext block →recent activity
Analyzing
Block #74,434,448
20 transactions · 13 stateful · 2026-05-14 01:08:01 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,434,448 · 20 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
1w02w13w09w010w111w212w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631f96f4…d10e
0xd32edf…ff58
7 touches
6 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0xce8bbe33…b72e
0x3bd359…433a
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xc3483764…f299
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
6 conflicts on slot 0x631f96f47a…59d10e
Audit this contract →
← previous block·next block →recent activity