← previous blocknext block →recent activity
Analyzing
Block #73,394,042
24 transactions · 16 stateful · 2026-05-09 05:26:13 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,394,042 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w011w113w214w316w217w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0xfefffad9…77d0
0xd32edf…ff58
5 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity