← previous blocknext block →recent activity
Analyzing
Block #74,346,186
9 transactions · 8 stateful · 2026-05-13 15:20:32 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,346,186 · 9 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x6ddd6f49…59b8
0x065c9d…c394
3 touches
1 conflict
0x6b28e7a9…556d
0x065c9d…c394
2 touches
0 conflicts
0x6b8942bb…ba8a
0x065c9d…c394
2 touches
0 conflicts
0x7ae22077…e5f2
0x065c9d…c394
2 touches
0 conflicts
0xb862178c…cc1a
0x065c9d…c394
2 touches
0 conflicts
0xc525c7b5…75a2
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity