← previous blocknext block →recent activity
Analyzing
Block #75,756,658
9 transactions · 9 stateful · 2026-05-20 04:27:53 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,756,658 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf286b7b…769a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6feb7d6a…4fbb
0x065c9d…c394
3 touches
1 conflict
0x0dc2f678…a5c7
0x065c9d…c394
2 touches
0 conflicts
0x5d95d489…f947
0x065c9d…c394
2 touches
0 conflicts
0xa30df210…643b
0x065c9d…c394
2 touches
0 conflicts
0xdfa159d0…1576
0x065c9d…c394
2 touches
0 conflicts
0xff43917b…d80a
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 0xbf286b7b41…07769a
Audit this contract →
← previous block·next block →recent activity