← previous blocknext block →recent activity
Analyzing
Block #74,434,437
30 transactions · 21 stateful · 2026-05-14 01:07:57 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,434,437 · 30 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
2w03w17w08w212w015w016w120w021w122w223w325w427w529w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36741168…1763
0xd32edf…ff58
9 touches
10 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0xce8bbe33…b72e
0x3bd359…433a
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
10 conflicts on slot 0x36741168c8…181763
Audit this contract →
← previous block·next block →recent activity