← previous blocknext block →recent activity
Analyzing
Block #76,569,906
12 transactions · 10 stateful · 2026-05-23 22:45:30 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,569,906 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xb2dc007e…83bd
0xd32edf…ff58
3 touches
1 conflict
0x24bad2b5…a600
0x065c9d…c394
2 touches
0 conflicts
0x70ca57bd…5eb1
0x065c9d…c394
2 touches
0 conflicts
0x72795c69…3c94
0x065c9d…c394
2 touches
0 conflicts
0xbdec5498…6aeb
0x065c9d…c394
2 touches
0 conflicts
0xda3df11c…1705
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity