← previous blocknext block →recent activity
Analyzing
Block #72,286,410
13 transactions · 11 stateful · 2026-05-04 02:29:54 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,286,410 · 13 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdcbb5ade…0a6c
0x065c9d…c394
4 touches
1 conflict
0x5c22b89e…44e8
0x065c9d…c394
3 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x3a0f254c…ef06
0x065c9d…c394
2 touches
0 conflicts
0x460a08f3…60f2
0x065c9d…c394
2 touches
0 conflicts
0xd943a92f…7c2a
0x065c9d…c394
2 touches
0 conflicts
0xded17b51…de9a
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