← previous blocknext block →recent activity
Analyzing
Block #75,162,702
7 transactions · 6 stateful · 2026-05-17 10:14:14 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,162,702 · 7 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f6df0bf…c491
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xdbe870e5…4850
0x065c9d…c394
3 touches
1 conflict
0x1b17dd2a…1d13
0x065c9d…c394
3 touches
1 conflict
0x5ee8e24e…8981
0x065c9d…c394
2 touches
0 conflicts
0x95578c98…e427
0x065c9d…c394
2 touches
0 conflicts
0xde1fde46…406e
0x065c9d…c394
2 touches
0 conflicts
0xf97a8ebf…8dd7
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 0x5f6df0bff5…51c491
Audit this contract →
← previous block·next block →recent activity