← previous blocknext block →recent activity
Analyzing
Block #72,370,439
7 transactions · 7 stateful · 2026-05-04 11:50:09 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,370,439 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c72b24b…a078
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ba91518…2094
0x065c9d…c394
3 touches
1 conflict
0x70a3259d…2c95
0x065c9d…c394
3 touches
1 conflict
0xd2078ebe…4eb0
0x065c9d…c394
2 touches
0 conflicts
0xd8593350…b13d
0x065c9d…c394
2 touches
0 conflicts
0xed0c29b5…e315
0x065c9d…c394
2 touches
0 conflicts
0xf166a5e2…b6af
0x065c9d…c394
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 0x9c72b24b60…31a078
Audit this contract →
← previous block·next block →recent activity