That's weird. How is a transaction that conflict with another transaction with
63084 confirmations still be accepted by nodes? The transaction you posted will never confirm. I'd guess the older transaction got double spended too.
Edit:
Looks like
This transaction was made a year ago. The one who made it need to rescan their wallet.
then double spend dont have solution?
Just tell the sender to send again and check the input carefully or clean their wallet first using -zapwallettxes (instructions
here). zapwallettxes will delete all unconfirmed transaction from a wallet and they will reappear after they get confirmed.
Unless the sender do this they might get the same problem in the future.
Edit:
Forgot to mention that this is if they're using bitcoin core.
I dont think its that easy. This is all kinds of fucked up. As you wrote yourself why is it shown as having 63k confirmations and unconfirmed at the same time?
Here is the decoded TX (B)

{
"txid": "1a7d0db89beb6fa643263a9cf1c7c95646404bff37522e7be1c62bfa08962c56",
"hash": "1a7d0db89beb6fa643263a9cf1c7c95646404bff37522e7be1c62bfa08962c56",
"size": 225,
"vsize": 225,
"version": 1,
"locktime": 0,
"vin": [
{
"txid": "fb77d308677b9b7c2cd1e3f1a2ca8e478cb988f1efb5afd3ffb1c4817487f09f",
"vout": 1,
"scriptSig": {
"asm": "304402204c1e26a3fa559f79ebcaf0393d66a0d4b008bee6cb8bf30ed469853efd6be2f602202c42ea9b078385bbce082dbe6ea0c4e09ad1ee445af8f54e0ba9c5679650e8a7[ALL] 030172577180dcd5e90427061d95dc75eea853a7d6284cecde3d4b892a0e6fc459",
"hex": "47304402204c1e26a3fa559f79ebcaf0393d66a0d4b008bee6cb8bf30ed469853efd6be2f602202c42ea9b078385bbce082dbe6ea0c4e09ad1ee445af8f54e0ba9c5679650e8a70121030172577180dcd5e90427061d95dc75eea853a7d6284cecde3d4b892a0e6fc459"
},
"sequence": 4294967295
}
],
"vout": [
{
"value": 0.08716124,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 97fdb65580e78e8bc02730968d7a0f962e7591b6 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a91497fdb65580e78e8bc02730968d7a0f962e7591b688ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"1EreyCicGPWf4jKtz8QfWnJkMv89HAkMX2"
]
}
},
{
"value": 1.62984678,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 5947c23a1ec58ae03419d0296eeceb6183680400 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a9145947c23a1ec58ae03419d0296eeceb618368040088ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"19956xNmRtwHojVZfVMXG3xHEovVARVWbK"
]
}
}
]
}
This[1] is the input (ID: 1) used. Its spend here[2]. Someone is playing with you OP.
[1]
https://www.blocktrail.com/BTC/tx/fb77d308677b9b7c2cd1e3f1a2ca8e478cb988f1efb5afd3ffb1c4817487f09f[2]
https://www.blocktrail.com/BTC/tx/cb2c291a8c083882c3a0eb2f43bf20c1cdba9e771ac6bb952fc200d4b274b679
