← previous blocknext block →recent activity
Analyzing
Block #73,399,034
9 transactions · 7 stateful · 2026-05-09 05:59:31 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,399,034 · 9 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
0x47e16a45…f5d4
0x065c9d…c394
4 touches
1 conflict
0x577be7b0…f53f
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4175119d…cdb1
0x065c9d…c394
3 touches
1 conflict
0x985f9233…26e6
0x065c9d…c394
3 touches
1 conflict
0xa4fc93ca…7b8f
0x065c9d…c394
3 touches
1 conflict
0x8bf3eae4…8661
0x065c9d…c394
3 touches
1 conflict
0xa295e8d1…5a55
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
1 conflict on slot 0x47e16a4548…56f5d4
Audit this contract →
← previous block·next block →recent activity