← previous blocknext block →recent activity
Analyzing
Block #75,522,943
15 transactions · 11 stateful · 2026-05-19 02:29:41 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,522,943 · 15 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
1w04w15w29w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2ad567a7…f71f
0xd32edf…ff58
5 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x21a02714…bae3
0x065c9d…c394
2 touches
0 conflicts
0x23ccd61c…706c
0x065c9d…c394
2 touches
0 conflicts
0x2fc2fa6a…8ff3
0x065c9d…c394
2 touches
0 conflicts
0x77fe8bae…3ab6
0x065c9d…c394
2 touches
0 conflicts
0x90f5c6a7…700a
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity