← previous blocknext block →recent activity
Analyzing
Block #76,465,884
10 transactions · 7 stateful · 2026-05-23 11:12:42 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,465,884 · 10 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
1w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x04bde8ff…b573
0x065c9d…c394
3 touches
1 conflict
0xbd12130b…9410
0x065c9d…c394
3 touches
1 conflict
0x20d4cbf5…168a
0x065c9d…c394
2 touches
0 conflicts
0x43cb0920…11d6
0x065c9d…c394
2 touches
0 conflicts
0x596fcccf…921d
0x065c9d…c394
2 touches
0 conflicts
0xa61e74c1…0aa5
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