← previous blocknext block →recent activity
Analyzing
Block #73,375,694
18 transactions · 17 stateful · 2026-05-09 03:24:09 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,375,694 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w09w112w613w717w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x838b9ab6…d286
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe038916c…b1be
0x2a68ba…90c5
8 touches
6 conflicts
0x249ebd16…5edc
0x065c9d…c394
4 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0xf0f673fd…37a7
0x8e764f…e322
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
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 0x838b9ab69c…56d286
Audit this contract →
← previous block·next block →recent activity