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.
f71a03d8708830ffec0ba83833f763bdc85b1d93c6d50e820693564c8e250456
Both payments are on their chains and locked to the same secret hash 8a1531bbf9f20395a1dfc3cfb0e6fb7de3541ad8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: f71a03d8708830ffec0ba83833f763bdc85b1d93c6d50e820693564c8e250456
5c616ed77d9fcfc86a81227bcc7b3a4dc135f4797b43e19d1a882c3cbdd492d0
Both payments are on their chains and locked to the same secret hash 8a1531bbf9f20395a1dfc3cfb0e6fb7de3541ad8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: d7055a2e3ca2f28433487e33494d45e5dedcb4e350ec2e207609879b2bfe9047
- TakerPaymentReceived: 5c616ed77d9fcfc86a81227bcc7b3a4dc135f4797b43e19d1a882c3cbdd492d0
- TakerPaymentSpent: 54e945fcdb38a51014e4af9d808b093c96a322d49aefacc45547048a28ce82b3
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.