pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,995,610
← previous block
next block →
recent activity
Analyzing
Block #70,995,610
13 transactions · 13 stateful · 2026-04-28 03:03:42 UTC
Parallelism
85
/100
Blocked
23
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,610
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x98717539
· blocks 1
#4
0x6463ffd1
#5
updateDataFeedsValuesPartial
#6
0xed82b078
#7
setData
#9
updatePrices
· blocks 1
#10
updatePrices
· blocks 1
#8
0x39435dac
#11
updatePrices
#12
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
9
w0
10
w0
11
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
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
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
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:
0x34b6552d…112a6f
1 conflict on slot
0xadac4a860c…a3c2bc
Audit this contract →
← previous block
·
next block →
recent activity