← previous blocknext block →recent activity
Analyzing
Block #72,214,935
8 transactions · 7 stateful · 2026-05-03 18:29:35 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,935 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbdc813a1…7854
0x065c9d…c394
4 touches
1 conflict
0xdab207c5…f7e3
0x065c9d…c394
4 touches
1 conflict
0xdffd26c9…17c2
0x065c9d…c394
3 touches
1 conflict
0x9ea8dc5d…4477
0x065c9d…c394
3 touches
1 conflict
0xccb498e0…807a
0x065c9d…c394
3 touches
1 conflict
0x6114220d…7b7a
0x065c9d…c394
2 touches
0 conflicts
0xb105afa5…a4f2
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity