pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,951,759
← previous block
next block →
recent activity
Analyzing
Block #70,951,759
11 transactions · 10 stateful · 2026-04-27 22:11:30 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,951,759
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xa96df62f
#3
0x9d329d8f
#4
0x6463ffd1
#5
updateDataFeedsValuesPartial
#6
setData
#7
updatePrices
· blocks 1
#8
updatePrices
· blocks 1
#9
updatePrices
#10
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w0
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x216dcb6f…765f
0x065c9d…c394
2 touches
0 conflicts
0x23d0d09a…183f
0x065c9d…c394
2 touches
0 conflicts
0x789ef430…34e2
0x065c9d…c394
2 touches
0 conflicts
0xc1f19aa0…1cd3
0x065c9d…c394
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:
0x8fd63afb…2f536c
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity