← previous blocknext block →recent activity
Analyzing
Block #75,023,001
6 transactions · 5 stateful · 2026-05-16 18:42:14 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,023,001 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa221f58f…b32c
0x065c9d…c394
4 touches
1 conflict
0x1e6ac0c1…d74a
0x065c9d…c394
3 touches
1 conflict
0xf9d7daf0…47bd
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x46541c9c…2c98
0x065c9d…c394
2 touches
0 conflicts
0x6eb6bbb3…c761
0x065c9d…c394
2 touches
0 conflicts
0x9c2f064f…68e2
0x065c9d…c394
2 touches
0 conflicts
0x262bb27b…6b2c
0x11ed3b…2c96
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 0xa221f58ff7…f9b32c
Audit this contract →
← previous block·next block →recent activity