← previous blocknext block →recent activity
Analyzing
Block #72,971,382
14 transactions · 14 stateful · 2026-05-07 06:34:02 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,971,382 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w27w08w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5d08ab9…e53d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x70b2f813…783c
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x44ad89ba…cf83
0x23c26b…7777
4 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
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
3 conflicts on slot 0xd5d08ab905…34e53d
Audit this contract →
← previous block·next block →recent activity