← previous blocknext block →recent activity
Analyzing
Block #76,482,040
11 transactions · 11 stateful · 2026-05-23 13:00:20 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,482,040 · 11 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x25168e36…d081
0x065c9d…c394
4 touches
1 conflict
0xe80a89b9…7236
0x065c9d…c394
3 touches
1 conflict
0x4b24adc0…89aa
0x065c9d…c394
3 touches
1 conflict
0x6d0a3dbf…5626
0x065c9d…c394
2 touches
0 conflicts
0xbd12130b…9410
0x065c9d…c394
2 touches
0 conflicts
0xe633bb1d…dc0d
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity