← previous blocknext block →recent activity
Analyzing
Block #76,114,709
16 transactions · 14 stateful · 2026-05-21 20:14:24 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,114,709 · 16 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
1w02w13w14w25w07w08w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0xd2d29721…e0fb
0x9f3832…4ae4
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x67d846dd…358c
0x6661d3…7777
4 touches
1 conflict
0x9527c4ff…73fb
0x6661d3…7777
4 touches
1 conflict
0x631ab234…2d48
0x9f3832…4ae4
4 touches
1 conflict
0x631ab234…2d49
0x9f3832…4ae4
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity