← previous blocknext block →recent activity
Analyzing
Block #76,083,342
11 transactions · 9 stateful · 2026-05-21 16:45:21 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,083,342 · 11 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7f39836…6592
0x065c9d…c394
4 touches
1 conflict
0x11e3f768…634e
0x065c9d…c394
3 touches
1 conflict
0x2130ff49…313f
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7e283f0d…b2e4
0x065c9d…c394
2 touches
0 conflicts
0x8f179633…a163
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x9bf064a6…4f04
0x2a68ba…90c5
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 0xc7f39836da…ae6592
Audit this contract →
← previous block·next block →recent activity