← previous blocknext block →recent activity
Analyzing
Block #75,015,587
22 transactions · 15 stateful · 2026-05-16 17:52:51 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,015,587 · 22 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
1w06w07w18w29w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21c137b8…3a77
0x3bd359…433a
6 touches
3 conflicts
0x4d394876…c488
0x402807…5159
6 touches
3 conflicts
0xb34209a2…164d
0x402807…5159
6 touches
3 conflicts
0x00000000…0008
0x509771…3c7b
6 touches
3 conflicts
0x502d89dc…83b4
0x065c9d…c394
2 touches
0 conflicts
0x853c1e8a…58ab
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
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