← previous blocknext block →recent activity
Analyzing
Block #76,477,935
12 transactions · 10 stateful · 2026-05-23 12:33:00 UTC
Parallelism
58/100
Blocked
40%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,477,935 · 12 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
2w03w14w25w36w09w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x1ae3e91c…aacd
0xd32edf…ff58
3 touches
1 conflict
0x03a389f3…a900
0x065c9d…c394
3 touches
1 conflict
0x07e8f365…3ea7
0x065c9d…c394
3 touches
1 conflict
0xa10f0082…e301
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: Market-MON/USDC
10 conflicts on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity