← previous blocknext block →recent activity
Analyzing
Block #73,374,413
14 transactions · 11 stateful · 2026-05-09 03:15:37 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,374,413 · 14 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
1w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0f2a0e87…dfd7
0x065c9d…c394
2 touches
0 conflicts
0x100cc983…ca76
0x065c9d…c394
2 touches
0 conflicts
0x38b8e0c5…bc58
0x065c9d…c394
2 touches
0 conflicts
0x4bc6515e…4838
0x065c9d…c394
2 touches
0 conflicts
0x90f503fd…cb72
0x065c9d…c394
2 touches
0 conflicts
0xd81a1719…9719
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity