This one took about 2.0× the usual for VRSC/DASH. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
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:23 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.
8bdda41dfcae3d8d1687acda36531d92622df6d1c5e8b38d92859d0a612e5d44
Both payments are on their chains and locked to the same secret hash 9733232115bb714d5142069c219d8abaafbd80e5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8bdda41dfcae3d8d1687acda36531d92622df6d1c5e8b38d92859d0a612e5d44
a7d00f14cbe06ab2369f7404f6d95e740d98b04d45c32ec58104fea20b6509fb
Both payments are on their chains and locked to the same secret hash 9733232115bb714d5142069c219d8abaafbd80e5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a57d10f6520a0008c649f98d7560007320dbc26cc3f4216cf688f7af6fa07ea7
- TakerPaymentSent · TakerPaymentReceived: a7d00f14cbe06ab2369f7404f6d95e740d98b04d45c32ec58104fea20b6509fb
- TakerPaymentSpent: de6bc9c96f7f32d3c303f7c82b34c0a7453571c69a17002b3d11e7738fa63893
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.