← previous blocknext block →recent activity
Analyzing
Block #75,687,635
13 transactions · 11 stateful · 2026-05-19 20:48:43 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,687,635 · 13 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
1w03w04w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd0696c7c…c482
0x065c9d…c394
3 touches
1 conflict
0x5c14829a…92a3
0x065c9d…c394
3 touches
1 conflict
0x65e2ab88…6bf2
0x065c9d…c394
3 touches
1 conflict
0x60bd100a…c777
0x065c9d…c394
2 touches
0 conflicts
0x619835a4…96bb
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 0xdfa159d0ee…971576
Audit this contract →
← previous block·next block →recent activity