← previous blocknext block →recent activity
Analyzing
Block #73,434,417
10 transactions · 9 stateful · 2026-05-09 09:54:55 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,434,417 · 10 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
4w06w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x73333fea…bf03
0x065c9d…c394
4 touches
1 conflict
0x2fc5406c…4e7b
0x065c9d…c394
2 touches
0 conflicts
0xa57cf562…c98f
0x065c9d…c394
2 touches
0 conflicts
0xc10ceaa2…3c7d
0x065c9d…c394
2 touches
0 conflicts
0xd21803ae…dfc4
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