pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,986,431
← previous block
next block →
recent activity
Analyzing
Block #70,986,431
12 transactions · 10 stateful · 2026-04-28 02:02:32 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,986,431
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#7
0x69f015b0
#8
setData
#9
0x39435dac
#10
updatePrices
#11
updatePrices
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b95477…89be
0x065c9d…c394
4 touches
1 conflict
0x22baa844…b52f
0x065c9d…c394
4 touches
1 conflict
0x66bb0ace…cba0
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xe532957e…7fa1
0x065c9d…c394
3 touches
1 conflict
0xc17bf20f…8c64
0x065c9d…c394
3 touches
1 conflict
0x8c799b2e…0f7f
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
0x20b95477c3…e889be
Audit this contract →
← previous block
·
next block →
recent activity