pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,996,712
← previous block
next block →
recent activity
Analyzing
Block #70,996,712
11 transactions · 10 stateful · 2026-04-28 03:11:01 UTC
Parallelism
73
/100
Blocked
40
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,712
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x67098489
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x69f025bd
#7
updatePrices
· blocks 1
#8
updatePrices
· blocks 1
#2
0xccf50a51
· blocks 1
#9
updatePrices
#10
updatePrices
#3
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w0
8
w0
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0001
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xbe7a4aad…70d4
0x065c9d…c394
3 touches
1 conflict
0x09beabbc…065e
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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…000000
Audit this contract →
← previous block
·
next block →
recent activity