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.
e836962a7d6edd579f23cf17def77fa157597f33269cb1676f2aab27a85170dd
Both payments are on their chains and locked to the same secret hash 29b282b9921e1fe562dbe26c031016677f928169, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e836962a7d6edd579f23cf17def77fa157597f33269cb1676f2aab27a85170dd
- MakerPaymentSpent: 8c10a012129932ef8202f80c0c385a0e28ed2af75c71968bd3fbf501de8143b9
b58b68b89a8d056b084f6a4e82bdb03edafb16a27089cb744cd596b1751f2824
Both payments are on their chains and locked to the same secret hash 29b282b9921e1fe562dbe26c031016677f928169, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 00894c5a9958885d6ac84cc91c22c1e5cc30bdc19efedfc4b9d0b700944bb7a5
- TakerPaymentSent · TakerPaymentReceived: b58b68b89a8d056b084f6a4e82bdb03edafb16a27089cb744cd596b1751f2824
- TakerPaymentSpent: 473eacc30dc6600f9ea7f56dde72fe81eb7cf787fc00ca08f5644de6d200b40e
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-8762.