← previous blocknext block →recent activity
Analyzing
Block #75,668,618
14 transactions · 9 stateful · 2026-05-19 18:42:11 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,668,618 · 14 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1d7f4bde…a759
0xd32edf…ff58
3 touches
1 conflict
0x5662c6cf…cb69
0x065c9d…c394
2 touches
0 conflicts
0x8efe9378…1228
0x065c9d…c394
2 touches
0 conflicts
0x8f63de72…50d9
0x065c9d…c394
2 touches
0 conflicts
0xe1f97de7…0575
0x065c9d…c394
2 touches
0 conflicts
0xe82813b6…f86b
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 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity