pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,951,296
← previous block
next block →
recent activity
Analyzing
Block #70,951,296
14 transactions · 12 stateful · 2026-04-27 22:08:25 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,951,296
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
updatePrices
#3
transfer
#4
updateDataFeedsValuesPartial
#5
0xa2b51e97
#6
modifyLiquidities
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#10
0x39435dac
#11
0x39435dac
· blocks 1
#12
0x39435dac
#13
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xf86f9e31…8c7b
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x5b571ba0…f13a
0x98dc6e…8633
2 touches
0 conflicts
0x68faa0b9…14af
0x98dc6e…8633
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:
0x34b6552d…112a6f
1 conflict on slot
0xac808a2776…3282db
Audit this contract →
← previous block
·
next block →
recent activity