← previous blocknext block →recent activity
Analyzing
Block #72,977,153
17 transactions · 15 stateful · 2026-05-07 07:12:28 UTC
Parallelism
59/100
Blocked
60%
Avg conflicts / tx
1.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,977,153 · 17 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
2w03w14w25w06w18w39w410w511w615w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
10 touches
10 conflicts
0x47c1a8e8…f74a
0x34b655…2a6f
8 touches
6 conflicts
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0x4e5ebbf7…ae70
0xc8689a…ee79
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x70b2f813…783c
0x2a68ba…90c5
6 touches
3 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
6 touches
3 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity