← previous blocknext block →recent activity
Analyzing
Block #75,844,768
17 transactions · 14 stateful · 2026-05-20 14:15:37 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,844,768 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w07w18w212w315w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c956b24…4aae
0x065c9d…c394
6 touches
3 conflicts
0xff4a7a06…c102
0xd32edf…ff58
5 touches
3 conflicts
0xc0ed5d1b…be19
0x065c9d…c394
5 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 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 0x6c956b248d…784aae
Audit this contract →
← previous block·next block →recent activity