← previous blocknext block →recent activity
Analyzing
Block #70,951,094
34 transactions · 30 stateful · 2026-04-27 22:07:04 UTC
Parallelism
91/100
Blocked
37%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,951,094 · 34 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
2w05w112w014w115w020w021w122w123w224w125w026w227w129w230w031w132w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b28bf77…e53a
0x34b655…2a6f
4 touches
1 conflict
0x1c913164…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x3c83275e…d7c2
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity