← previous blocknext block →recent activity
Analyzing
Block #75,549,659
10 transactions · 8 stateful · 2026-05-19 05:27:49 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,549,659 · 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
1w02w14w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xed2d8cbd…92f9
0xd32edf…ff58
3 touches
1 conflict
0x03d855cb…175f
0x065c9d…c394
2 touches
0 conflicts
0x3ca9dbb5…ae2b
0x065c9d…c394
2 touches
0 conflicts
0x56fdf2e4…1295
0x065c9d…c394
2 touches
0 conflicts
0x81aedbed…8bb4
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
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