← previous blocknext block →recent activity
Analyzing
Block #75,947,076
10 transactions · 9 stateful · 2026-05-21 01:37:27 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,947,076 · 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
1w02w03w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x640ea3eb…1c80
0x541997…f5a0
4 touches
1 conflict
0x640ea3eb…1c81
0x541997…f5a0
4 touches
1 conflict
0x9436adee…0df7
0x541997…f5a0
4 touches
1 conflict
0x30da5c52…b89c
0x065c9d…c394
2 touches
0 conflicts
0x6fcc0525…92eb
0x065c9d…c394
2 touches
0 conflicts
0xd4d4a3c5…44c2
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
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