← previous blocknext block →recent activity
Analyzing
Block #74,804,096
24 transactions · 20 stateful · 2026-05-15 18:19:48 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,804,096 · 24 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
1w08w19w210w011w114w015w116w019w320w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x5d823e…89c6
4 touches
1 conflict
0x50997ada…364d
0x5d823e…89c6
4 touches
1 conflict
0xf0f673fd…37a7
0x5d823e…89c6
4 touches
1 conflict
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 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity