← previous blocknext block →recent activity
Analyzing
Block #75,003,537
10 transactions · 9 stateful · 2026-05-16 16:32:18 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,003,537 · 10 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
1w02w14w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x66b4e1d9…75fa
0xd32edf…ff58
3 touches
1 conflict
0xaef9ce85…bec6
0x065c9d…c394
2 touches
0 conflicts
0xc43b30e2…79e9
0x065c9d…c394
2 touches
0 conflicts
0xd5a488e8…714b
0x065c9d…c394
2 touches
0 conflicts
0xe8abc8bc…8c38
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 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity