← previous blocknext block →recent activity
Analyzing
Block #73,479,098
10 transactions · 9 stateful · 2026-05-09 14:52:15 UTC
Parallelism
40/100
Blocked
56%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,479,098 · 10 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
1w05w16w27w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x3544447f…1883
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0e73f926…bea0
0x065c9d…c394
3 touches
1 conflict
0x1f109f41…07d4
0x065c9d…c394
3 touches
1 conflict
0x65377b4e…53c3
0x065c9d…c394
2 touches
0 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