← previous blocknext block →recent activity
Analyzing
Block #73,533,106
21 transactions · 18 stateful · 2026-05-09 20:51:31 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
0.95
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,533,106 · 21 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
1w02w13w25w07w212w213w314w015w116w217w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18d02062…5ac5
0xd32edf…ff58
7 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a996
0x188d58…ea8e
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 0x18d0206249…8e5ac5
Audit this contract →
← previous block·next block →recent activity