pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,995,915
← previous block
next block →
recent activity
Analyzing
Block #70,995,915
11 transactions · 8 stateful · 2026-04-28 03:05:43 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,915
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
withdraw
#4
0x6463ffd1
· blocks 1
#6
forward
#7
0x69f0247f
#8
setData
#9
exactInputSingle
#10
updatePrices
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa02277c…538e
0x065c9d…c394
4 touches
1 conflict
0xb5704993…5417
0x065c9d…c394
4 touches
1 conflict
0xb9d2968c…8856
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xefde936f…e602
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xc7a1e198…0530
0x065c9d…c394
2 touches
1 conflict
0xe438e173…162d
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
0xaa02277c04…8c538e
Audit this contract →
← previous block
·
next block →
recent activity