An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
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. 16: old-consensus-branch-id (Expected 4dec4df0, found c8e71055)
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 still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles 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 timelock expired 2026-04-28 00:14:41 UTC, so the maker can take it back now. Checked 2026-11-16 03:23:18 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.
90ae55d7daec6e338bacc9be037f4fd96d2030c35e55146bd43a1fc621c7f9e3
Both payments are on their chains and locked to the same secret hash 10d172f0def77d194db594991b1d280cf52f41fa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 90ae55d7daec6e338bacc9be037f4fd96d2030c35e55146bd43a1fc621c7f9e3
e6e270d812b0078d192f5173307bdd50a03dc5ac0b7d56fab40af32a536b5c19
Both payments are on their chains and locked to the same secret hash 10d172f0def77d194db594991b1d280cf52f41fa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c0f786e12fcc6345d926754f646fdfe845eef96e4f249fad2c72c3c22e923113
- TakerPaymentSent · TakerPaymentReceived: e6e270d812b0078d192f5173307bdd50a03dc5ac0b7d56fab40af32a536b5c19
- TakerPaymentSpent: 2f4e213c98ca22cb7e2f0916e9f115199dbd81e46b2a56decd186592f6da3c06
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.