← previous blocknext block →recent activity
Analyzing
Block #72,400,339
10 transactions · 9 stateful · 2026-05-04 15:09:29 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,400,339 · 10 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
1w02w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc594ec10…74e0
0x065c9d…c394
4 touches
1 conflict
0x22560693…ebfb
0x065c9d…c394
4 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
4 touches
1 conflict
0x46adc421…4ad0
0x065c9d…c394
4 touches
1 conflict
0x5c48536d…a387
0x065c9d…c394
4 touches
1 conflict
0xde1e6613…a02e
0x065c9d…c394
3 touches
1 conflict
0x74012117…26dd
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity