← previous blocknext block →recent activity
Analyzing
Block #73,981,528
21 transactions · 19 stateful · 2026-05-11 22:53:01 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,981,528 · 21 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
1w02w03w16w07w09w110w211w312w013w114w215w316w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82af9f10…1018
0xd32edf…ff58
9 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xe6455d1f…1029
0x754704…b603
6 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
6 touches
3 conflicts
0x09beabbc…065e
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
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 0x82af9f10b6…591018
Audit this contract →
← previous block·next block →recent activity