That is in the normal range for LBC/BCH. 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:1803] mm2src\coins\utxo\ "utxo_common:1186] utxo_common:1139] rpc_clients:2378] UnexpectedEnd"
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:33 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.
dc3e1788e8c10d61e3f7ae711d80a4fd174203d13c0b75de8092e054c9be3700
Both payments are on their chains and locked to the same secret hash e028a5da53a0db07573a2ee4dd626e7a9081abee, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dc3e1788e8c10d61e3f7ae711d80a4fd174203d13c0b75de8092e054c9be3700
7e0d948a879baa455d773f949c5a95663cf0e081874042e75242f1a7f2a8244d
Both payments are on their chains and locked to the same secret hash e028a5da53a0db07573a2ee4dd626e7a9081abee, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 448f0c786265cb2d36252e72967f1c4ef0a402eaeef1e44f35011b30ea6549fd
- TakerPaymentSent · TakerPaymentReceived: 7e0d948a879baa455d773f949c5a95663cf0e081874042e75242f1a7f2a8244d
- TakerPaymentSpent: 9c4dea08ae6763d4c1b669e1b844db1ceab841eb50e0ec6b08afea47846843d7
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.