← previous blocknext block →recent activity
Analyzing
Block #75,734,600
13 transactions · 10 stateful · 2026-05-20 02:01:12 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,734,600 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x075156fc…55e1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd5468d30…d96e
0x065c9d…c394
3 touches
1 conflict
0x3a32ebf6…7f76
0x065c9d…c394
3 touches
1 conflict
0x3375a2a6…e2dc
0x065c9d…c394
2 touches
0 conflicts
0x40bbd833…e307
0x065c9d…c394
2 touches
0 conflicts
0x7287510e…1cdc
0x065c9d…c394
2 touches
0 conflicts
0x73682ad3…b09b
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
1 conflict on slot 0x075156fc7f…1d55e1
Audit this contract →
← previous block·next block →recent activity