← previous blocknext block →recent activity
Analyzing
Block #75,336,069
12 transactions · 9 stateful · 2026-05-18 05:33:25 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,336,069 · 12 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
0x4f5a2428…8834
0x065c9d…c394
3 touches
1 conflict
0x1f6d2c4f…d626
0x065c9d…c394
3 touches
1 conflict
0x153c0863…b4eb
0x065c9d…c394
2 touches
0 conflicts
0x238c97eb…bc06
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x463e77c7…2ce0
0x065c9d…c394
2 touches
0 conflicts
0x6f0a705e…d659
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