← previous blocknext block →recent activity
Analyzing
Block #75,015,503
9 transactions · 7 stateful · 2026-05-16 17:52:16 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,015,503 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3223dcb…654b
0x065c9d…c394
4 touches
1 conflict
0x5c591f2b…379f
0x065c9d…c394
3 touches
1 conflict
0xfc75c460…8b05
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1f1100fb…0be0
0x065c9d…c394
2 touches
0 conflicts
0x24dc28f3…0427
0x065c9d…c394
2 touches
0 conflicts
0x3bbc5236…5c22
0x065c9d…c394
2 touches
0 conflicts
0x95a33771…ff8d
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 0xa3223dcb9a…cf654b
Audit this contract →
← previous block·next block →recent activity