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.
a2eae8d56374f9de0aaba40618c1b267bd582131c3487195a823071ce5893ffc
Both payments are on their chains and locked to the same secret hash 833dad1a09e1d6e7f4229ef8c71ad4dc17e14f73, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a2eae8d56374f9de0aaba40618c1b267bd582131c3487195a823071ce5893ffc
- MakerPaymentSpent: 2c265be4cc3dfbf26c095de7af5d478ba38e919563ec958831452d5e4c1ded2f
5551b7e2102b198d579f3017e97e18b616f4c2818cc6c1230cf3e99b7f0be9cd
Both payments are on their chains and locked to the same secret hash 833dad1a09e1d6e7f4229ef8c71ad4dc17e14f73, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1febb6e418495e642558f84eb634413a6080689ad5b85d12be8e5ad77f205094
- TakerPaymentSent · TakerPaymentReceived: 5551b7e2102b198d579f3017e97e18b616f4c2818cc6c1230cf3e99b7f0be9cd
- TakerPaymentSpent: 0258eb0a024f3a2c8c0b4c328e17a25b45a618a568e1c94c36bf0cbdd9c98949
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.