← previous blocknext block →recent activity
Analyzing
Block #75,302,709
11 transactions · 7 stateful · 2026-05-18 01:50:13 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,302,709 · 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
1w03w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0xbafc2a0e…3f14
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4401f7a4…1cf5
0x065c9d…c394
3 touches
1 conflict
0xa1cc27c7…2411
0x065c9d…c394
3 touches
1 conflict
0xe6feb0b5…ab3c
0x065c9d…c394
2 touches
0 conflicts
0xec1be96f…32cc
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity