← previous blocknext block →recent activity
Analyzing
Block #73,352,962
17 transactions · 16 stateful · 2026-05-09 00:53:02 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,352,962 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w08w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x65099a49…7fcc
0x065c9d…c394
4 touches
1 conflict
0xe7535190…5a0f
0xaba216…a862
4 touches
1 conflict
0xe94e77ab…f017
0xaba216…a862
4 touches
1 conflict
0xd821ae10…fe17
0xc8689a…ee79
4 touches
1 conflict
0xbdff944d…447e
0x2a68ba…90c5
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity