← previous blocknext block →recent activity
Analyzing
Block #74,518,691
14 transactions · 7 stateful · 2026-05-14 10:30:04 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,518,691 · 14 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x72fbfb06…ae5a
0x065c9d…c394
2 touches
0 conflicts
0x7a60ecba…e42e
0x065c9d…c394
2 touches
0 conflicts
0x86e1625c…eb07
0x065c9d…c394
2 touches
0 conflicts
0xe8805f31…806c
0x065c9d…c394
2 touches
0 conflicts
0xec1bc330…72c0
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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity