← previous blocknext block →recent activity
Analyzing
Block #75,893,397
13 transactions · 10 stateful · 2026-05-20 19:40:11 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,893,397 · 13 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
1w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x43a292c6…c1a9
0x065c9d…c394
2 touches
0 conflicts
0x441b29bb…883a
0x065c9d…c394
2 touches
0 conflicts
0xaa180bb9…7908
0x065c9d…c394
2 touches
0 conflicts
0xc0d14334…25ba
0x065c9d…c394
2 touches
0 conflicts
0xf195fc19…1a3a
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity