If you are already running a Virtual Machine with Windows 10, there is a native installation of Inkscape available from a Windows installer at the Inkscape site. The Inkscape build has a boatload of other package dependencies and MacPorts will need to compile and install them before it gets around to that Inkscape package. Any package that MacPorts downloads will require at minimum, the Command-line Tools (macOS 10.14) for Xcode 10.2.1 (macOS 10.14.3+), or the huge Xcode 10.2.1 installation. Xcode 11 is still in beta, and may not be intended for Mojave, or even stable.
Inkscape dot org suggests that although the MacPorts build of Inkscape does offer a native macOS build, it is a very early build and more reliability would exist in using the X11 build that would require XQuartz which has not been updated since 2016. As much as I would like Inkscape on macOS, I don't want the extra baggage of all those dependency packages installed to use it.
As a self-proclaimed newbie, attempting a MacPorts installation of Inkscape could well be too much (unsupported) headache to bother on macOS.