← previous blocknext block →recent activity
Analyzing
Block #73,533,046
10 transactions · 9 stateful · 2026-05-09 20:51:07 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,533,046 · 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
3w04w15w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x0c4de2e1…a293
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x576b9d47…4ae8
0x065c9d…c394
3 touches
1 conflict
0x2206ff4b…b370
0x065c9d…c394
3 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
1 conflict on slot 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity