← previous blocknext block →recent activity
Analyzing
Block #72,214,950
8 transactions · 7 stateful · 2026-05-03 18:29:41 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,214,950 · 8 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f997197…23c8
0x065c9d…c394
4 touches
1 conflict
0xdab207c5…f7e3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xab82af92…debe
0x065c9d…c394
3 touches
1 conflict
0xd5baa078…dca7
0x065c9d…c394
3 touches
1 conflict
0x551ae5c7…7d63
0x065c9d…c394
2 touches
0 conflicts
0x6114220d…7b7a
0x065c9d…c394
2 touches
0 conflicts
0x74fcce5c…b52a
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 0x4f99719726…b523c8
Audit this contract →
← previous block·next block →recent activity