pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,892,217
← previous block
next block →
recent activity
Analyzing
Block #70,892,217
13 transactions · 10 stateful · 2026-04-27 15:35:04 UTC
Parallelism
85
/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,892,217
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69ef829f
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
forward
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x6463ffd1
· blocks 1
#10
updatePriceFeedsIfNecessary
#11
forward
#12
0x69ef829f
#9
0x6463ffd1
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
0xbc3461ec…62c2
0x065c9d…c394
4 touches
1 conflict
0x34c72c1c…401e
0x065c9d…c394
4 touches
1 conflict
0x43517295…a82a
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3cce96aa…46c0
0x065c9d…c394
4 touches
1 conflict
0x39af984b…6e9b
0x065c9d…c394
2 touches
1 conflict
0x39af984b…6e9c
0x065c9d…c394
2 touches
1 conflict
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:
0x065c9d28…a9c394
1 conflict on slot
0xbc3461ec06…b262c2
Audit this contract →
← previous block
·
next block →
recent activity