← previous blocknext block →recent activity
Analyzing
Block #73,808,717
10 transactions · 9 stateful · 2026-05-11 03:41:39 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,808,717 · 10 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
2w04w05w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x371cbf19…1d16
0x065c9d…c394
2 touches
0 conflicts
0x7de04e42…4e46
0x065c9d…c394
2 touches
0 conflicts
0xb38c557c…de7b
0x065c9d…c394
2 touches
0 conflicts
0xfc23dc3d…1b6a
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity