← previous blocknext block →recent activity
Analyzing
Block #75,949,804
13 transactions · 10 stateful · 2026-05-21 01:55:35 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,949,804 · 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x32898b4d…277f
0x065c9d…c394
2 touches
0 conflicts
0x3b441fb6…25c0
0x065c9d…c394
2 touches
0 conflicts
0x4107a1af…0c26
0x065c9d…c394
2 touches
0 conflicts
0x80508db7…3dd6
0x065c9d…c394
2 touches
0 conflicts
0x944abe60…57d6
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 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity