pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,951,657
← previous block
next block →
recent activity
Analyzing
Block #70,951,657
12 transactions · 10 stateful · 2026-04-27 22:10:49 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,951,657
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
collect
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x69efdf61
· blocks 1
#6
0x69efdf61
#7
setData
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
#11
0x39435dac
#5
0x69efdf61
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2f1c865b…052a
0x3bd359…433a
2 touches
0 conflicts
0x4c770fe0…b972
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0xe527656e…2164
0x714a26…182d
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity