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 c8e71055, found c2d6d0b4)
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-16 07:23:35 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.
d3ee994a9a75d0bfd78a22e64480ad6f0d6679315e879c42db9e04b3360cfc08
Both payments are on their chains and locked to the same secret hash b968a96f26faf79ed82403c6e8c695afaa45e795, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: d3ee994a9a75d0bfd78a22e64480ad6f0d6679315e879c42db9e04b3360cfc08
df7553495f10ca03466cc2ff347e2e11e3692c6fac4f80eb6a5bd3a671b1c7fd
Both payments are on their chains and locked to the same secret hash b968a96f26faf79ed82403c6e8c695afaa45e795, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: df2247d0b323f3870f5af46e43cbe156d78f8f35f1d33d3ac97fcb8f4495fdc8
- TakerPaymentSent · TakerPaymentReceived: df7553495f10ca03466cc2ff347e2e11e3692c6fac4f80eb6a5bd3a671b1c7fd
- TakerPaymentSpent: e54a361b6856a4843dc6ff9a6055157a5f7da2b6c6b2680f90ea01a00276c606
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.