← previous blocknext block →recent activity
Analyzing
Block #76,112,323
16 transactions · 13 stateful · 2026-05-21 19:58:26 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,112,323 · 16 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
1w02w15w27w39w411w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
8 touches
6 conflicts
0xc0af25f8…9759
0x065c9d…c394
7 touches
6 conflicts
0x7615bc2d…5115
0x699abc…6a3b
4 touches
1 conflict
0x83676b0d…220a
0x699abc…6a3b
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3db9409…c641
0xd32edf…ff58
3 touches
1 conflict
0x9c5adf8c…b287
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
6 conflicts on slot 0x99a2130578…57dffc
Audit this contract →
← previous block·next block →recent activity