← previous blocknext block →recent activity
Analyzing
Block #74,034,215
9 transactions · 9 stateful · 2026-05-12 04:45:17 UTC
Parallelism
44/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,034,215 · 9 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
2w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x1b649e55…eb30
0x065c9d…c394
2 touches
0 conflicts
0x1ec9de9c…0c1f
0x065c9d…c394
2 touches
0 conflicts
0x22e45f04…bae7
0x065c9d…c394
2 touches
0 conflicts
0x2ae102b1…a6c4
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