← previous blocknext block →recent activity
Analyzing
Block #75,309,534
10 transactions · 9 stateful · 2026-05-18 02:35:59 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,309,534 · 10 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5bb9bbe…be30
0x065c9d…c394
4 touches
1 conflict
0x12d6c876…a33a
0x065c9d…c394
3 touches
1 conflict
0xcb79177f…9dac
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5fd82c61…bc0a
0x065c9d…c394
2 touches
0 conflicts
0x6a2a4111…2650
0x065c9d…c394
2 touches
0 conflicts
0x6c130c65…557c
0x065c9d…c394
2 touches
0 conflicts
0x738892e5…f0ad
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 0xf5bb9bbe7b…3fbe30
Audit this contract →
← previous block·next block →recent activity