← previous blocknext block →recent activity
Analyzing
Block #73,035,952
22 transactions · 16 stateful · 2026-05-07 13:43:49 UTC
Parallelism
73/100
Blocked
56%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,035,952 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w211w312w013w114w217w218w419w521w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x10dce475…4fd2
0x065c9d…c394
6 touches
3 conflicts
0x4e5ebbf7…ae70
0xc8689a…ee79
6 touches
3 conflicts
0x1a4b4152…0a08
0x6ca43f…c331
6 touches
3 conflicts
0x3e4b8d9f…b8a7
0x6ca43f…c331
6 touches
3 conflicts
0x5b3dfef8…a676
0x6ca43f…c331
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity