← previous blocknext block →recent activity
Analyzing
Block #75,677,402
11 transactions · 9 stateful · 2026-05-19 19:40:45 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,677,402 · 11 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
1w02w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x99b47661…94db
0x065c9d…c394
4 touches
1 conflict
0xe975bda9…44c3
0x065c9d…c394
4 touches
1 conflict
0x646fe6c9…e8b0
0x065c9d…c394
3 touches
1 conflict
0xf597a0dd…af36
0x065c9d…c394
3 touches
1 conflict
0x6a88a5f7…c4a8
0x065c9d…c394
3 touches
1 conflict
0x6b1b771c…f43e
0x065c9d…c394
3 touches
1 conflict
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