← previous blocknext block →recent activity
Analyzing
Block #75,932,062
13 transactions · 12 stateful · 2026-05-20 23:57:27 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,932,062 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xbcba919f…4cf5
0xd32edf…ff58
3 touches
1 conflict
0x4057cb80…8c8f
0x065c9d…c394
2 touches
0 conflicts
0x4e971aa0…1622
0x065c9d…c394
2 touches
0 conflicts
0x6e5b1818…8cc4
0x065c9d…c394
2 touches
0 conflicts
0x9c33ff85…5a54
0x065c9d…c394
2 touches
0 conflicts
0xc8a3e8af…e283
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity