← previous blocknext block →recent activity
Analyzing
Block #71,744,534
17 transactions · 10 stateful · 2026-05-01 14:14:59 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,744,534 · 17 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
1w03w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21f20950…c7f2
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9999108f…b1a9
0x065c9d…c394
4 touches
1 conflict
0xdd1542ef…a9dc
0x065c9d…c394
3 touches
1 conflict
0x42f28791…72c1
0x065c9d…c394
3 touches
1 conflict
0x1a4b4152…0a08
0x33663b…4897
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 0x21f2095002…1ac7f2
Audit this contract →
← previous block·next block →recent activity