← previous blocknext block →recent activity
Analyzing
Block #73,638,171
10 transactions · 9 stateful · 2026-05-10 08:31:31 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,638,171 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x02995091…50cd
0x065c9d…c394
2 touches
0 conflicts
0x1e100817…5c85
0x065c9d…c394
2 touches
0 conflicts
0x398167bd…0689
0x065c9d…c394
2 touches
0 conflicts
0x3e1cd845…d52a
0x065c9d…c394
2 touches
0 conflicts
0x80bfe7fa…46a9
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
3 conflicts on slot 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity