pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,999,584
← previous block
next block →
recent activity
Analyzing
Block #70,999,584
12 transactions · 11 stateful · 2026-04-28 03:30:05 UTC
Parallelism
75
/100
Blocked
36
%
Avg conflicts / tx
0.42
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,999,584
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x6463ffd1
#4
setData
#5
0x39435dac
· blocks 1
#7
updatePrices
· blocks 2
#8
updatePrices
· blocks 1
#6
0x39435dac
#9
updatePrices
#10
updatePrices
· blocks 1
#11
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w0
9
w1
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x8fd63a…536c
6 touches
3 conflicts
0x00000000…0001
0x8fd63a…536c
6 touches
3 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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
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
3 conflicts on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity