← previous blocknext block →recent activity
Analyzing
Block #74,527,901
11 transactions · 8 stateful · 2026-05-14 11:32:04 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,527,901 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w28w19w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x76e559a4…77fb
0x2a68ba…90c5
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0xf6104a91…72c0
0xd32edf…ff58
3 touches
1 conflict
0x9c4691c7…8467
0x065c9d…c394
3 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
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
6 conflicts on slot 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity