← previous blocknext block →recent activity
Analyzing
Block #73,469,533
11 transactions · 7 stateful · 2026-05-09 13:48:40 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,469,533 · 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
3w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x40191596…cd63
0x065c9d…c394
2 touches
0 conflicts
0x575effc5…db85
0x065c9d…c394
2 touches
0 conflicts
0x66e90507…252d
0x065c9d…c394
2 touches
0 conflicts
0xb254a588…1201
0x065c9d…c394
2 touches
0 conflicts
0xf3a5ae89…1408
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 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity