← previous blocknext block →recent activity
Analyzing
Block #73,687,030
11 transactions · 10 stateful · 2026-05-10 14:01:01 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,687,030 · 11 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
3w06w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xbcb582f9…4583
0x065c9d…c394
3 touches
1 conflict
0x95914186…8423
0x065c9d…c394
3 touches
1 conflict
0x91ca2b02…d9f2
0x065c9d…c394
2 touches
0 conflicts
0x976c1abd…043e
0x065c9d…c394
2 touches
0 conflicts
0xea0b0ba6…30f7
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 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity