← previous blocknext block →recent activity
Analyzing
Block #73,753,740
18 transactions · 13 stateful · 2026-05-10 21:31:08 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,753,740 · 18 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
1w03w15w011w112w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb159af88…a9e7
0x065c9d…c394
8 touches
6 conflicts
0xf9e612bd…d6df
0xd32edf…ff58
5 touches
3 conflicts
0xae69c125…2379
0x2a68ba…90c5
4 touches
1 conflict
0x7f81fb82…633e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbfb555a9…419e
0x065c9d…c394
3 touches
1 conflict
0x0eea965f…2cca
0x065c9d…c394
3 touches
1 conflict
0x45137828…7bdf
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
6 conflicts on slot 0xb159af880b…47a9e7
Audit this contract →
← previous block·next block →recent activity