← previous blocknext block →recent activity
Analyzing
Block #72,286,443
24 transactions · 20 stateful · 2026-05-04 02:30:07 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,286,443 · 24 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
2w03w04w15w29w012w114w215w316w117w218w419w521w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x24de5cd5…9828
0x065c9d…c394
4 touches
1 conflict
0x2efd1e50…71e3
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