0xe2ca8411…971dsent to0x8759196a…8f78·#4,633,715·view on Etherscan
I just realized why. It's probably because wallet.metamask.io has a setting to switch the network, and the default isn't the mainnet (can't remember what the default was.) I'm at aws re:invent this week, so I probably wont have time to look into the issue until this weekend. There's likely a way to default the provider to the mainnet unless the user has specified another network on wallet.metamask.io