← previous blocknext block →recent activity
Analyzing
Block #72,972,407
21 transactions · 20 stateful · 2026-05-07 06:40:50 UTC
Parallelism
57/100
Blocked
60%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #72,972,407 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w314w415w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x7f189cf6…afab
0x065c9d…c394
14 touches
21 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
10 touches
10 conflicts
0x3b8ffd61…f3ad
0x34b655…2a6f
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x60a4aa96…6b08
0x065c9d…c394
6 touches
5 conflicts
0x4e5ebbf7…ae70
0xc8689a…ee79
6 touches
3 conflicts
0x70b2f813…783c
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity