← previous blocknext block →recent activity
Analyzing
Block #73,324,642
10 transactions · 9 stateful · 2026-05-08 21:44:37 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,324,642 · 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x6fe22e12…1f3a
0x065c9d…c394
2 touches
0 conflicts
0xc093e254…1fdc
0x065c9d…c394
2 touches
0 conflicts
0xe2a78273…4047
0x065c9d…c394
2 touches
0 conflicts
0xf604cae4…afde
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 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity