← previous blocknext block →recent activity
Analyzing
Block #76,211,883
11 transactions · 7 stateful · 2026-05-22 07:01:11 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,211,883 · 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
1w03w14w25w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x2c543b14…3c40
0x065c9d…c394
3 touches
1 conflict
0x0ba887b8…6d86
0x065c9d…c394
2 touches
0 conflicts
0x0dde3d75…0764
0x065c9d…c394
2 touches
0 conflicts
0x36cd6c60…8550
0x065c9d…c394
2 touches
0 conflicts
0x5d246264…fb50
0x065c9d…c394
2 touches
0 conflicts
0xcbf2d5a4…f6f1
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