← previous blocknext block →recent activity
Analyzing
Block #74,518,547
23 transactions · 20 stateful · 2026-05-14 10:29:05 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,518,547 · 23 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
1w03w14w25w06w17w28w011w012w114w315w320w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x9d388269…d270
0x065c9d…c394
4 touches
1 conflict
0xe57c1266…dbee
0x065c9d…c394
4 touches
1 conflict
0x23bbc51d…668c
0x065c9d…c394
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
6 conflicts on slot 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity