← previous blocknext block →recent activity
Analyzing
Block #72,980,350
26 transactions · 18 stateful · 2026-05-07 07:33:44 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,980,350 · 26 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
1w03w05w07w18w211w012w114w315w416w517w518w622w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f2daa28…fbc7
0xd32edf…ff58
15 touches
28 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xcad937e9…7872
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
28 conflicts on slot 0x1f2daa2818…0cfbc7
Audit this contract →
← previous block·next block →recent activity