That is in the normal range for VRSC/DASH. 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.
the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation)
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:15:25 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.
9a09a375b706812e13bb62309cd6e719090f09e764d889cd443b85ee1737af45
Both payments are on their chains and locked to the same secret hash be3050403a477bf18fad0f96285ac66c0335471a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9a09a375b706812e13bb62309cd6e719090f09e764d889cd443b85ee1737af45
fd4292ccf0c15cf20e4bfce1f0610d36d0997eccad36cc7124725e08bcc626e2
Both payments are on their chains and locked to the same secret hash be3050403a477bf18fad0f96285ac66c0335471a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0dc0d2009425bf1ca4b46bfdbd13127ad28c66adce0ec79844b3646affb32242
- TakerPaymentSent · TakerPaymentReceived: fd4292ccf0c15cf20e4bfce1f0610d36d0997eccad36cc7124725e08bcc626e2
- TakerPaymentSpent: 549db8294ac4ba2cd02af4aff2420af80389390ece8cd3964aacacd5ac4fb8a1
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 defistats-gleec.