← previous blocknext block →recent activity
Analyzing
Block #72,296,856
24 transactions · 21 stateful · 2026-05-04 03:40:01 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,296,856 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w010w011w112w214w117w218w319w420w521w623w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
6 touches
3 conflicts
0xe89e1a22…ce49
0x8d66a4…3095
6 touches
3 conflicts
0x820ff274…b287
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity