← previous blocknext block →recent activity
Analyzing
Block #70,986,207
8 transactions · 8 stateful · 2026-04-28 02:01:03 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,986,207 · 8 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
1w04w15w2
- 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
0x3e62b818…8be9
0x065c9d…c394
4 touches
1 conflict
0x7881933e…e75c
0x065c9d…c394
4 touches
1 conflict
0xa1c36ae3…49e4
0x065c9d…c394
4 touches
1 conflict
0xd9792552…6ba4
0x065c9d…c394
4 touches
1 conflict
0x78117b9c…a7a7
0x065c9d…c394
2 touches
1 conflict
0x7c1724ab…019e
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