← previous blocknext block →recent activity
Analyzing
Block #72,400,331
8 transactions · 7 stateful · 2026-05-04 15:09:26 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,400,331 · 8 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
2w03w15w06w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46adc421…4ad0
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0de208df…d056
0x065c9d…c394
3 touches
1 conflict
0xd13e9060…bb11
0x065c9d…c394
3 touches
1 conflict
0xe57036d8…8f45
0x065c9d…c394
3 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 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
3 conflicts on slot 0x46adc4217f…2b4ad0
Audit this contract →
← previous block·next block →recent activity