← previous blocknext block →recent activity
Analyzing
Block #73,394,046
25 transactions · 17 stateful · 2026-05-09 05:26:15 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,394,046 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w110w112w215w317w419w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5840b9f3…7942
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe038916c…b1be
0x2a68ba…90c5
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x9b30c5ca…93f7
0x065c9d…c394
3 touches
1 conflict
0x1d91fc94…0835
0x065c9d…c394
3 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 0x5840b9f3d2…f67942
Audit this contract →
← previous block·next block →recent activity