← previous blocknext block →recent activity
Analyzing
Block #72,971,595
13 transactions · 13 stateful · 2026-05-07 06:35:27 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,971,595 · 13 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
1w02w15w06w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x7e39990f…68c7
0x065c9d…c394
4 touches
1 conflict
0x8ae5221b…8cd6
0x065c9d…c394
4 touches
1 conflict
0xa070ffa8…6892
0x065c9d…c394
4 touches
1 conflict
0xa6792a6d…94af
0x065c9d…c394
4 touches
1 conflict
0xbc2c49fe…36f3
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity