← previous blocknext block →recent activity
Analyzing
Block #75,046,873
9 transactions · 8 stateful · 2026-05-16 21:21:17 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,046,873 · 9 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
1w04w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x55e8ea86…7971
0x065c9d…c394
4 touches
1 conflict
0x7bab646a…5e72
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x29afeea7…8527
0x065c9d…c394
2 touches
0 conflicts
0x4d51d41d…87aa
0x065c9d…c394
2 touches
0 conflicts
0x6fb0c708…8971
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
3 conflicts on slot 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity