← previous blocknext block →recent activity
Analyzing
Block #75,016,523
7 transactions · 7 stateful · 2026-05-16 17:59:07 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,016,523 · 7 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a5ea178…4f8b
0x065c9d…c394
4 touches
1 conflict
0x470b88d2…1d5f
0x065c9d…c394
4 touches
1 conflict
0xa1ecb354…508b
0x065c9d…c394
3 touches
1 conflict
0x0c4ab97b…3b2c
0x065c9d…c394
3 touches
1 conflict
0xbdee9ce9…5398
0x065c9d…c394
3 touches
1 conflict
0xfe6ab5ad…5673
0x065c9d…c394
3 touches
1 conflict
0xac03461d…53d5
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
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 0x5a5ea178a9…644f8b
Audit this contract →
← previous block·next block →recent activity