← previous blocknext block →recent activity
Analyzing
Block #74,188,633
10 transactions · 8 stateful · 2026-05-12 21:52:44 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,188,633 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf823e97f…2ee6
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x5da7d26f…e59e
0x065c9d…c394
2 touches
0 conflicts
0x97d4d7c8…caf0
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xcf652486…8323
0x065c9d…c394
2 touches
0 conflicts
0xe2c4d139…a557
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity