pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,560,038
← previous block
next block →
recent activity
Analyzing
Block #71,560,038
13 transactions · 9 stateful · 2026-04-30 17:46:49 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,560,038
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f39600
#2
0x69f39600
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
0x69f39600
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#10
0x39435dac
#11
0x39435dac
· blocks 1
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
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
0x00000000…0002
0x7e9d3a…9fda
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
0x1b5d2e607a…9999b5
Audit this contract →
← previous block
·
next block →
recent activity