← previous blocknext block →recent activity
Analyzing
Block #73,034,265
20 transactions · 14 stateful · 2026-05-07 13:32:36 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,034,265 · 20 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
1w02w13w04w07w115w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1faa7c1f…09a5
0x065c9d…c394
3 touches
1 conflict
0x5b6ab1ad…6270
0x065c9d…c394
3 touches
1 conflict
0x5b3f0036…5773
0xd32edf…ff58
3 touches
1 conflict
0xf2e24723…1987
0x065c9d…c394
3 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
3 conflicts on slot 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity