← previous blocknext block →recent activity
Analyzing
Block #72,318,175
21 transactions · 17 stateful · 2026-05-04 06:02:01 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,318,175 · 21 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
1w05w08w010w111w212w313w414w516w619w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf4ac35c…4300
0xd32edf…ff58
13 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb81
0x1b6862…e19c
4 touches
1 conflict
0x5069b288…1eb7
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
3 touches
1 conflict
0xf18c956e…ab13
0x699abc…6a3b
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 0xaf4ac35c9a…174300
Audit this contract →
← previous block·next block →recent activity