← previous blocknext block →recent activity
Analyzing
Block #72,311,361
11 transactions · 10 stateful · 2026-05-04 05:16:39 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,311,361 · 11 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
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51439a0d…d9b1
0x065c9d…c394
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x76049dc1…4708
0x065c9d…c394
3 touches
1 conflict
0xe0e612c1…7f14
0x065c9d…c394
3 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
2 touches
0 conflicts
0xff14abc8…2231
0x065c9d…c394
2 touches
0 conflicts
0x74e71984…ae90
0x2a68ba…90c5
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
1 conflict on slot 0x51439a0d01…4fd9b1
Audit this contract →
← previous block·next block →recent activity