← previous blocknext block →recent activity
Analyzing
Block #75,948,545
8 transactions · 7 stateful · 2026-05-21 01:47:13 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,948,545 · 8 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
1w06w17w2
- 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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d569537…1f74
0x065c9d…c394
2 touches
0 conflicts
0x1a9293e8…b4ad
0x065c9d…c394
2 touches
0 conflicts
0x57d7b62f…47cc
0x065c9d…c394
2 touches
0 conflicts
0x6239b9b9…9859
0x065c9d…c394
2 touches
0 conflicts
0xda108069…8ccc
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