← previous blocknext block →recent activity
Analyzing
Block #72,971,760
29 transactions · 17 stateful · 2026-05-07 06:36:32 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,971,760 · 29 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
1w03w14w015w119w222w323w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x7f189cf6…afab
0x065c9d…c394
6 touches
3 conflicts
0x55acc6dc…f4b3
0xd32edf…ff58
5 touches
3 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x2e2f2b55…f197
0x065c9d…c394
4 touches
1 conflict
0x2fb6ddd2…b2a4
0x000000…012a
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
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