← previous blocknext block →recent activity
Analyzing
Block #73,416,599
11 transactions · 11 stateful · 2026-05-09 07:56:26 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,416,599 · 11 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
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x1e06cc60…c988
0x065c9d…c394
4 touches
1 conflict
0x9cabc1ba…285a
0x065c9d…c394
4 touches
1 conflict
0x7c6eb682…5e4f
0x065c9d…c394
3 touches
1 conflict
0x4dbc4dbf…4fb6
0x065c9d…c394
3 touches
1 conflict
0xa59f0f80…5129
0x065c9d…c394
3 touches
1 conflict
0xaf8ddcb9…2795
0x065c9d…c394
3 touches
1 conflict
0xe6cf0ee0…f721
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: MarginAccount
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity