← previous blocknext block →recent activity
Analyzing
Block #76,462,496
9 transactions · 7 stateful · 2026-05-23 10:50:06 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,462,496 · 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5f616f94…5911
0xd32edf…ff58
3 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x7e098218…dd69
0x065c9d…c394
2 touches
0 conflicts
0xc37feee8…da4b
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xfc20c342…976f
0x065c9d…c394
2 touches
0 conflicts
0xfe0f395d…e46c
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