← previous blocknext block →recent activity
Analyzing
Block #75,932,232
8 transactions · 7 stateful · 2026-05-20 23:58:35 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,932,232 · 8 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2ab3d4d…7ef5
0x065c9d…c394
4 touches
1 conflict
0xd9c8e367…92d3
0x065c9d…c394
3 touches
1 conflict
0x9b45a5e5…243f
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xac2b8221…d18c
0x065c9d…c394
2 touches
0 conflicts
0xc40a299f…545d
0x065c9d…c394
2 touches
0 conflicts
0xc6e5dffd…0524
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
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
1 conflict on slot 0xb2ab3d4d06…867ef5
Audit this contract →
← previous block·next block →recent activity