← previous blocknext block →recent activity
Analyzing
Block #73,743,807
16 transactions · 11 stateful · 2026-05-10 20:24:06 UTC
Parallelism
63/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,743,807 · 16 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
1w02w09w110w212w313w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a628f0b…6eb6
0xd32edf…ff58
11 touches
15 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
4 touches
1 conflict
0x006ba84c…97b3
0x065c9d…c394
3 touches
1 conflict
0x00000000…000a
0x09f880…ede0
2 touches
0 conflicts
0xdc7a27e1…d536
0x754704…b603
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
15 conflicts on slot 0x0a628f0b2c…176eb6
Audit this contract →
← previous block·next block →recent activity