Quote from: skrubalov on March 14, 2014, 08:41:23 AM

01000000035f90504209b8ceb52bb41e99ec805b655637ef54db25a26e520ad97c7849955e01000 0008b483045022033c3ed7183b2c82b39f9028f6eccdd7950a46b7d3eb2408aaa2d4c222f38a728 022100f07975f8e0b3092a3509c1fca92c8b4d4ebcf3f3d9d0eb36754c2847b8323c45014104a55 ae122dde8a0da3fc8bf8f8cf1c577af3e0afa93bcbeefe2992ebd2e21224164b669dd9dd278decb 025c73d89d78888e2575158e388e204a7c8790b83d9f32ffffffff9fd4080c3424c82a200dde1b8 bb8d099c0f37ba34136ad2489ec149e9b28890e0d0000008c49304602210099cd1df56ef56d404f ce7a36b93fc5a83e704604a33f411c64c7cbb9a96c187f0221008361d7eb73365862f5f2eaf1882 d563a589477c85f1ffb742eb6e1bb01071422014104c9eb0121abfae01b7c0a50d9f33c76522a29 581050e259069b4535dfa896b4ca5ec7561a010faa5112f3c07021ade1b17b66276e6e2e60862ea 6257e8aefec15ffffffff1393ad08bc6dfd77ce6cbad31dd39f2049614b9f84c5fe4a4fb138ef27 5fb09e130000008a47304402200f4caa01db1dbc00963d3a3462f3ca143a786ca5b632d48d1dea3 b4dd1cca0140220097ffeb14fe9950bb002a80eb4d192834c3c16fe14ed40111ac599375d6ea468 014104c9eb0121abfae01b7c0a50d9f33c76522a29581050e259069b4535dfa896b4ca5ec7561a0 10faa5112f3c07021ade1b17b66276e6e2e60862ea6257e8aefec15ffffffff0280969800000000 001976a914f77086feabeedf663f21baabb79c250820be2b3388acb1d21c00000000001976a9144 51bd6821c3155716ef8fd0fe6e36c3369a889b588ac00000000

10x

I think that's the wrong transaction. That's transaction ID 1da82bcaa7be41ca4c0c3fbc0fd35adc8d855e3af40be19323889fc41453a4a8, sending BTC0.1 to 1PZLhvDs8S7rhq349DHFjuXs2smSEttNUJ. Huh

In any case, my node had no problem pushing it. There's no fee, but none is needed (if you don't mind waiting a long time for confirmations), and all inputs are confirmed and not double-spent. I've no idea why blockchain.info seems to hate it.