pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,956,601
← previous block
next block →
recent activity
Analyzing
Block #70,956,601
12 transactions · 11 stateful · 2026-04-27 22:43:45 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,956,601
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x6463ffd1
· blocks 1
#4
setData
#6
delegate
#7
0x39435dac
#8
updatePrices
· blocks 1
#9
updatePrices
· blocks 1
#5
0x6463ffd1
#10
updatePrices
#11
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w0
9
w0
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00b17183…36d9
0x065c9d…c394
4 touches
1 conflict
0xce08610f…47ec
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0001
0x8fd63a…536c
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity