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.
0a8151d79d1c81ece3bb4004383d43250f4a2f860bf35465e939893089498583
Both payments are on their chains and locked to the same secret hash 5a4622637bfdc4a356172d3d1d8b037016696315, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0a8151d79d1c81ece3bb4004383d43250f4a2f860bf35465e939893089498583
- MakerPaymentSpent: 302222aee488ec29fc137b5c9b58e4620993f6a1d5bbe34aafc2e9962e5cb67e
aedf10e541f393653160e7e730148024d6b01c07f14dc32e015ebd0ef429d0c1
Both payments are on their chains and locked to the same secret hash 5a4622637bfdc4a356172d3d1d8b037016696315, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cf7efbd433f7ade60e449507adb42c4fe38a9a5d1587459f5bffa906c79a683e
- TakerPaymentSent · TakerPaymentReceived: aedf10e541f393653160e7e730148024d6b01c07f14dc32e015ebd0ef429d0c1
- TakerPaymentSpent: 72a62319792beb117ed759aee68220b46828b29fc1ce5c56d3491875a7708e19
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.