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.
36b6771b5e9d3be8dd010d0cad6239b156d2d8000431cf5bc2dd1015676bf760
Both payments are on their chains and locked to the same secret hash 5fcfd276163d245613f6660638476866e2f03945, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 36b6771b5e9d3be8dd010d0cad6239b156d2d8000431cf5bc2dd1015676bf760
- MakerPaymentSpent: 625fdc3d946d69372b820cb7285b4b56899a1e7fa9c72c7a359b5f8f1c209baa
1138c8f8b0706e0376b1a3afe1dec59fc6d927f886d666a2d82f386f837cbe1c
Both payments are on their chains and locked to the same secret hash 5fcfd276163d245613f6660638476866e2f03945, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 41e9f59bd456116434ee9f0a549b188abbef4df5796984d0d13931b685d6a037
- TakerPaymentSent · TakerPaymentReceived: 1138c8f8b0706e0376b1a3afe1dec59fc6d927f886d666a2d82f386f837cbe1c
- TakerPaymentSpent: 1db4ce4cb25331455b16671e0c6df22059d0dd467fb632e9a3db2353e5bac136
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.