pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,998,680
← previous block
next block →
recent activity
Analyzing
Block #70,998,680
12 transactions · 10 stateful · 2026-04-28 03:24:08 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,998,680
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f028cf
#2
updateDataFeedsValuesPartial
#3
0x6463ffd1
#4
0x0c7abd22
#5
0x96e62922
#6
0x69f028cf
#7
setData
#8
0x39435dac
· blocks 1
#10
updatePrices
#11
updatePrices
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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