pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,845,573
← previous block
next block →
recent activity
Analyzing
Block #70,845,573
10 transactions · 8 stateful · 2026-04-27 10:24:27 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,845,573
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb3dd4ec4
#2
updatePrices
#3
addLiquidity
#4
0x6463ffd1
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x69ef39d3
#9
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
0x4a27b231…434d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x08fc3429…16d4
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xdb0e25f0…f13e
0x065c9d…c394
3 touches
1 conflict
0xafb9463d…0bae
0x065c9d…c394
3 touches
1 conflict
0x27007746…0502
0x754704…b603
2 touches
0 conflicts
0xa3dc6f35…13e9
0x754704…b603
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
0x4a27b23191…d9434d
Audit this contract →
← previous block
·
next block →
recent activity