← previous blocknext block →recent activity
Analyzing
Block #75,846,565
14 transactions · 12 stateful · 2026-05-20 14:27:41 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,846,565 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xc99365ba…801e
0x065c9d…c394
3 touches
1 conflict
0x1cc93ae6…4e1d
0x188d58…ea8e
2 touches
0 conflicts
0x0219372e…792e
0x29e8a6…7777
2 touches
0 conflicts
0xd06cc746…27e4
0x29e8a6…7777
2 touches
0 conflicts
0x11e1e2a4…54fb
0x34b655…2a6f
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