← previous blocknext block →recent activity
Analyzing
Block #75,032,584
10 transactions · 8 stateful · 2026-05-16 19:46:04 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,032,584 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf533c8dd…a211
0xd32edf…ff58
3 touches
1 conflict
0x3ff2589f…7641
0x065c9d…c394
2 touches
0 conflicts
0x4dfcc0c9…2a4e
0x065c9d…c394
2 touches
0 conflicts
0x5df51046…d4a8
0x065c9d…c394
2 touches
0 conflicts
0x72b99fc8…eb11
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