← previous blocknext block →recent activity
Analyzing
Block #76,490,711
9 transactions · 7 stateful · 2026-05-23 13:58:07 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,490,711 · 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
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x21301c6f…c661
0x065c9d…c394
2 touches
0 conflicts
0x75bf5a20…0588
0x065c9d…c394
2 touches
0 conflicts
0xc43f395a…51fc
0x065c9d…c394
2 touches
0 conflicts
0xdc6d6e2e…899b
0x065c9d…c394
2 touches
0 conflicts
0xdcbad2c3…6452
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