pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,955,772
← previous block
next block →
recent activity
Analyzing
Block #70,955,772
8 transactions · 7 stateful · 2026-04-27 22:38:13 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,955,772
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
0x39abec6b
#7
setData
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ce3d006…85fb
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x3da11c10…aa48
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6a08f30b…402a
0x065c9d…c394
3 touches
1 conflict
0x382f3a72…a324
0x065c9d…c394
3 touches
1 conflict
0x1e0379d3…ab3a
0x065c9d…c394
2 touches
1 conflict
0x0eafd69f…a721
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
1 conflict on slot
0x3ce3d006eb…b785fb
Audit this contract →
← previous block
·
next block →
recent activity