← previous blocknext block →recent activity
Analyzing
Block #75,744,239
12 transactions · 12 stateful · 2026-05-20 03:05:20 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,744,239 · 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x73531a61…f785
0x065c9d…c394
4 touches
1 conflict
0x4e0d0225…107b
0x065c9d…c394
3 touches
1 conflict
0x383dd6a3…75a2
0x065c9d…c394
2 touches
0 conflicts
0xe2516ece…c5da
0x065c9d…c394
2 touches
0 conflicts
0xe2c5c08f…6d63
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
2 touches
0 conflicts
0xa17ec269…7cdd
0x1d1325…2305
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