← previous blocknext block →recent activity
Analyzing
Block #71,697,327
9 transactions · 9 stateful · 2026-05-01 09:00:35 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,697,327 · 9 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
3w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x882f9b0b…d062
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8c35db2e…7912
0x065c9d…c394
3 touches
1 conflict
0x3cac5b2b…30d3
0x065c9d…c394
3 touches
1 conflict
0x2fef4fa6…7f49
0x065c9d…c394
3 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x738b60d0…3f25
0x065c9d…c394
2 touches
0 conflicts
0xd63729fb…c0ec
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 0x882f9b0b59…fbd062
Audit this contract →
← previous block·next block →recent activity