← previous blocknext block →recent activity
Analyzing
Block #76,110,096
9 transactions · 8 stateful · 2026-05-21 19:43:36 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,110,096 · 9 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
1w02w13w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x324cb0fe…02df
0x065c9d…c394
2 touches
0 conflicts
0x40f146e0…bc05
0x065c9d…c394
2 touches
0 conflicts
0x659a07bb…aeed
0x065c9d…c394
2 touches
0 conflicts
0x9767f7d4…19a6
0x065c9d…c394
2 touches
0 conflicts
0xc83086eb…6c75
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity