← previous blocknext block →recent activity
Analyzing
Block #73,502,565
20 transactions · 16 stateful · 2026-05-09 17:28:30 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,502,565 · 20 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
5w07w18w29w310w011w112w213w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x687d11d0…8083
0x065c9d…c394
4 touches
1 conflict
0xd5260e32…5b08
0x065c9d…c394
3 touches
1 conflict
0xbc45165f…688e
0x065c9d…c394
3 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