← previous blocknext block →recent activity
Analyzing
Block #75,134,339
9 transactions · 7 stateful · 2026-05-17 07:04:55 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,134,339 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9b12eae…c056
0x065c9d…c394
4 touches
1 conflict
0x9fdcd41a…2425
0x065c9d…c394
3 touches
1 conflict
0x09d35c80…ab0e
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x3bbc5236…5c22
0x065c9d…c394
2 touches
0 conflicts
0x40f70e84…1cb0
0x065c9d…c394
2 touches
0 conflicts
0x4e8a01d7…82b2
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 0xd9b12eaecc…56c056
Audit this contract →
← previous block·next block →recent activity