← previous blocknext block →recent activity
Analyzing
Block #75,680,075
9 transactions · 9 stateful · 2026-05-19 19:58:30 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,680,075 · 9 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
1w02w03w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xdbf1cb37…c9db
0x065c9d…c394
3 touches
1 conflict
0x17897640…6c45
0x065c9d…c394
3 touches
1 conflict
0x24b73616…d074
0x065c9d…c394
2 touches
0 conflicts
0x50fcb03f…186c
0x065c9d…c394
2 touches
0 conflicts
0x512bbf59…a2c4
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 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity