← previous blocknext block →recent activity
Analyzing
Block #76,668,555
11 transactions · 9 stateful · 2026-05-24 09:42:16 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,668,555 · 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23c9a846…1e26
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x240d09d4…37e0
0x065c9d…c394
3 touches
1 conflict
0xbad16f16…55da
0x065c9d…c394
3 touches
1 conflict
0xc252d664…f54b
0x065c9d…c394
3 touches
1 conflict
0xcfb22522…f08b
0x065c9d…c394
2 touches
0 conflicts
0xfbcf9807…fe6e
0x065c9d…c394
2 touches
0 conflicts
0xd06cc746…27e4
0x163569…0b07
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 0x23c9a84637…0e1e26
Audit this contract →
← previous block·next block →recent activity