That is in the normal range for LCC/DOGE. The time a swap takes is set mostly by the block spacing of the two chains involved, so a pair with slow blocks is slow for everyone, every time.
The record stops at MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.
taker_swap:1806] "utxo_common:1258] utxo_common:1211] rpc_clients:2330] JsonRpcError { client_info: "coin: LCC", request: JsonRpcRequest { jsonrpc: "2.0", id: "712", method: " ", params: }, error: Transport("All electrums are currently disconnected") }"
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch it. Whether it was retried is a question for the chain rather than for this log.
The chain shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin. The secret is public, so the taker's claim can still be made; the maker can take it back after the timelock. Checked 2026-11-06 05:55:02 UTC. It will be asked again.
Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.
355b433dc2c7ae19f6b789999ee44f8941e6b6b15f8172f4385a133119b38ca6
Both payments are on their chains and locked to the same secret hash aacd8566b8e9ff051349818920ee648071222e35, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 355b433dc2c7ae19f6b789999ee44f8941e6b6b15f8172f4385a133119b38ca6
92f98e86865ab233dd02584cccd0a79190b9ddbc8841b5bf5096fbfd86a05e1e
Both payments are on their chains and locked to the same secret hash aacd8566b8e9ff051349818920ee648071222e35, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 26c99ceb008756cd7f1905b44c8fc33b121f76971f8c5719d8d0d917e2bb5d85
- TakerPaymentSent · TakerPaymentReceived: 92f98e86865ab233dd02584cccd0a79190b9ddbc8841b5bf5096fbfd86a05e1e
- TakerPaymentSpent: 734b61579836a5178be86701decf886a7b72764f4abac9278152cc64b6e32767
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.