← previous blocknext block →recent activity
Analyzing
Block #73,611,259
10 transactions · 9 stateful · 2026-05-10 05:30:49 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,611,259 · 10 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
1w02w13w24w35w07w49w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32a6b582…ffd6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x58e06bab…34ce
0x1b6862…e19c
4 touches
1 conflict
0x8240d70c…7c3b
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
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
6 conflicts on slot 0x32a6b58283…63ffd6
Audit this contract →
← previous block·next block →recent activity