← previous blocknext block →recent activity
Analyzing
Block #75,051,612
8 transactions · 7 stateful · 2026-05-16 21:52:52 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,051,612 · 8 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
3w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x37460074…fad0
0x065c9d…c394
2 touches
0 conflicts
0x4e2a5ea7…a10d
0x065c9d…c394
2 touches
0 conflicts
0x5a456a3e…08e0
0x065c9d…c394
2 touches
0 conflicts
0xa38a7002…6c84
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity