← previous blocknext block →recent activity
Analyzing
Block #76,462,762
8 transactions · 7 stateful · 2026-05-23 10:51:51 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,462,762 · 8 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0xf32affd6…d4ac
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9a83d4e4…3057
0x065c9d…c394
3 touches
1 conflict
0x46cf66a8…dd8b
0x065c9d…c394
3 touches
1 conflict
0x218f8bbf…a746
0x065c9d…c394
2 touches
0 conflicts
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x29811d8b…bc27
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 0x49cbdb1b43…f7bda4
Audit this contract →
← previous block·next block →recent activity