← previous blocknext block →recent activity
Analyzing
Block #71,041,610
7 transactions · 6 stateful · 2026-04-28 08:09:49 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,041,610 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x21b3c0ff…2a6b
0x065c9d…c394
4 touches
1 conflict
0xa62a7aef…ee84
0x065c9d…c394
4 touches
1 conflict
0xce5f7a8b…d675
0x065c9d…c394
4 touches
1 conflict
0xd28d4f05…f4fa
0x065c9d…c394
4 touches
1 conflict
0x869e6e32…3804
0x065c9d…c394
2 touches
1 conflict
0x9aae6849…5e2f
0x065c9d…c394
2 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity