pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,089,937
← previous block
next block →
recent activity
Analyzing
Block #71,089,937
15 transactions · 10 stateful · 2026-04-28 13:31:46 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,089,937
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
multicall
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#10
updatePrices
· blocks 1
#11
updatePrices
· blocks 2
#12
updatePrices
· blocks 1
#13
updatePrices
#14
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w0
12
w1
13
w1
14
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
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x447d9f0e…9f0f
0x73ada1…8be0
2 touches
0 conflicts
0x508a54af…1846
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42f7
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42fa
0x73ada1…8be0
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