← previous blocknext block →recent activity
Analyzing
Block #72,972,206
22 transactions · 20 stateful · 2026-05-07 06:39:30 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,972,206 · 22 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
1w02w03w14w05w18w09w111w213w214w315w416w520w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
8 touches
6 conflicts
0x251861eb…78fd
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x02e6e909…f06f
0x065c9d…c394
6 touches
3 conflicts
0x150af51d…9c42
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity