← previous blocknext block →recent activity
Analyzing
Block #73,398,382
12 transactions · 11 stateful · 2026-05-09 05:55:11 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,398,382 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0xac22227d…9e5c
0x065c9d…c394
4 touches
1 conflict
0x152478dd…0510
0x065c9d…c394
4 touches
1 conflict
0xf3c67367…dfa9
0x065c9d…c394
3 touches
1 conflict
0x342abf1a…71bd
0x065c9d…c394
3 touches
1 conflict
0x8bafe618…0641
0x065c9d…c394
3 touches
1 conflict
0xa49a7f1d…56bc
0x065c9d…c394
3 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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity