pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,891,965
← previous block
next block →
recent activity
Analyzing
Block #70,891,965
14 transactions · 11 stateful · 2026-04-27 15:33:23 UTC
Parallelism
79
/100
Blocked
18
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,891,965
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#3
0x69ef823a
#5
0x5bf9264c
#6
0x5bf9264c
#7
0x69ef823a
#8
forward
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x785f5745
#12
0x39435dac
#13
updatePrices
#2
updatePrices
· blocks 1
#4
swapAndForwardEth
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x30b54477…fe3b
0x000000…012a
2 touches
0 conflicts
0x45aeff3b…5e52
0x000000…012a
2 touches
0 conflicts
0x5c0d27d4…c4dd
0x000000…012a
2 touches
0 conflicts
0x9a7f04e9…c7a1
0x000000…012a
2 touches
0 conflicts
0xc54f9533…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…000b
0x097d40…9920
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:
0xb857c13a…1a9be1
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity