← previous blocknext block →recent activity
Analyzing
Block #76,245,650
9 transactions · 7 stateful · 2026-05-22 10:46:35 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,245,650 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f0098a8…5ce7
0x065c9d…c394
4 touches
1 conflict
0x536d53b1…9dc2
0x065c9d…c394
3 touches
1 conflict
0xadc831c8…44cf
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0c5d3f46…81e5
0x065c9d…c394
2 touches
0 conflicts
0x16df9608…5922
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x5b46b2ef…6043
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 0x3f0098a825…2c5ce7
Audit this contract →
← previous block·next block →recent activity