← previous blocknext block →recent activity
Analyzing
Block #75,839,728
18 transactions · 11 stateful · 2026-05-20 13:41:39 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,839,728 · 18 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
1w05w06w19w110w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0xf722d24e…ac24
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x24b73616…d074
0x065c9d…c394
3 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x451469f0…5c65
0x34b655…2a6f
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