← previous blocknext block →recent activity
Analyzing
Block #75,760,099
9 transactions · 7 stateful · 2026-05-20 04:50:49 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,760,099 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c26183d…9263
0x065c9d…c394
4 touches
1 conflict
0x37eada69…a22f
0x065c9d…c394
3 touches
1 conflict
0x8f410d28…ee2c
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xb808001c…1c53
0x065c9d…c394
2 touches
0 conflicts
0xc34dfac2…5723
0x065c9d…c394
2 touches
0 conflicts
0xd30c1355…21f7
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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
1 conflict on slot 0x2c26183ddb…329263
Audit this contract →
← previous block·next block →recent activity