← previous blocknext block →recent activity
Analyzing
Block #73,359,811
15 transactions · 11 stateful · 2026-05-09 01:38:25 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,359,811 · 15 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
1w02w16w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x0e7a136d…735c
0x065c9d…c394
4 touches
1 conflict
0x21c3fbdb…ace5
0x065c9d…c394
4 touches
1 conflict
0x422f85e2…50f8
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0xf0ca1c42…03da
0x065c9d…c394
4 touches
1 conflict
0xf628f113…3ce3
0x065c9d…c394
4 touches
1 conflict
0x8d0dfe2c…3345
0x2a68ba…90c5
4 touches
1 conflict
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 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity