pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,908,842
← previous block
next block →
recent activity
Analyzing
Block #70,908,842
16 transactions · 14 stateful · 2026-04-27 17:25:47 UTC
Parallelism
88
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,842
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
exec
#4
updatePriceFeedsIfNecessary
#5
0xb0435a94
#6
forward
#7
forward
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0x69ef9c92
#11
setData
#12
updatePrices
· blocks 1
#13
updatePrices
· blocks 1
#14
updatePrices
#15
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
13
w0
14
w1
15
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
0x2906176a…85b6
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
2 touches
0 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1542
0x34b655…2a6f
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