← previous blocknext block →recent activity
Analyzing
Block #73,038,771
31 transactions · 20 stateful · 2026-05-07 14:02:35 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,038,771 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w07w08w115w216w117w218w019w322w323w424w529w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf1f328ea…fae5
0xd32edf…ff58
7 touches
6 conflicts
0x70b2f813…783c
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x2fcfec1d…dbf4
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x7e7cffb9…6074
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity