← previous blocknext block →recent activity
Analyzing
Block #76,212,704
10 transactions · 9 stateful · 2026-05-22 07:06:44 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,212,704 · 10 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
1w02w13w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0000
0x2f946a…11eb
4 touches
1 conflict
0x0d10fe50…7670
0x065c9d…c394
4 touches
1 conflict
0xf288b1b7…81c0
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x0e3b3138…15e6
0x065c9d…c394
2 touches
0 conflicts
0x56c53f1d…9723
0x065c9d…c394
2 touches
0 conflicts
0x84c54cab…769a
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