← previous blocknext block →recent activity
Analyzing
Block #74,600,693
9 transactions · 6 stateful · 2026-05-14 19:41:42 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,600,693 · 9 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35e90c3c…188d
0x065c9d…c394
4 touches
1 conflict
0x8b9c2321…513b
0x065c9d…c394
3 touches
1 conflict
0xd94d342b…7ed9
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2aa789c7…d6bb
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
2 touches
0 conflicts
0xbea59939…b035
0x065c9d…c394
2 touches
0 conflicts
0xc82baee2…b6be
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 0x35e90c3c0d…79188d
Audit this contract →
← previous block·next block →recent activity