← previous blocknext block →recent activity
Analyzing
Block #73,524,745
20 transactions · 16 stateful · 2026-05-09 19:55:57 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,524,745 · 20 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
1w02w15w08w09w110w211w015w216w317w418w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x679db184…ec7d
0xd32edf…ff58
7 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf8480e2a…dfef
0x1b6862…e19c
6 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 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 0x679db18405…53ec7d
Audit this contract →
← previous block·next block →recent activity