← previous blocknext block →recent activity
Analyzing
Block #73,753,430
17 transactions · 13 stateful · 2026-05-10 21:29:03 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,753,430 · 17 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
1w02w13w24w35w49w011w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26103a1a…92dd
0xd32edf…ff58
9 touches
10 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
6 touches
3 conflicts
0x9ef83c66…4437
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…189c
0x1b6862…e19c
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 0x26103a1a8d…0892dd
Audit this contract →
← previous block·next block →recent activity