← previous blocknext block →recent activity
Analyzing
Block #75,599,722
9 transactions · 9 stateful · 2026-05-19 11:01:20 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,599,722 · 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
1w03w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1a789076…5bbf
0x065c9d…c394
2 touches
0 conflicts
0x320d484a…dc37
0x065c9d…c394
2 touches
0 conflicts
0xa486ee06…8cae
0x065c9d…c394
2 touches
0 conflicts
0xae797080…f0a6
0x065c9d…c394
2 touches
0 conflicts
0xf66c41d6…1365
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