← previous blocknext block →recent activity
Analyzing
Block #73,375,417
18 transactions · 15 stateful · 2026-05-09 03:22:18 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,375,417 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w29w212w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe038916c…b1be
0x2a68ba…90c5
6 touches
3 conflicts
0xdca61130…f4c8
0xd32edf…ff58
5 touches
3 conflicts
0xec43b680…299e
0x065c9d…c394
5 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
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: MarginAccount
3 conflicts on slot 0xe038916c87…fab1be
Audit this contract →
← previous block·next block →recent activity