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.
9e13317a35e35b39bd454466b7f86299c03933c2bdbc4d3d1840122bd12d4ae2
Both payments are on their chains and locked to the same secret hash 6067cab4321c54fc9aa93c7c0ffd03789560ed35, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9e13317a35e35b39bd454466b7f86299c03933c2bdbc4d3d1840122bd12d4ae2
- MakerPaymentSpent: b33d14d5fa74b798b07ce82449ce322c966e1a2598a5441677ec6759d4d35116
8ce90cbdc83537c2ba2cd13c18a1680f172c0993f228282e1a1a13f797a84394
Both payments are on their chains and locked to the same secret hash 6067cab4321c54fc9aa93c7c0ffd03789560ed35, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bdf110b6e814abead942ae7d3c14c634b07a8a48b3b805be05e82c75664153ca
- TakerPaymentSent · TakerPaymentReceived: 8ce90cbdc83537c2ba2cd13c18a1680f172c0993f228282e1a1a13f797a84394
- TakerPaymentSpent: 2d2500173e30caabaf025f19fca18970524a9bb496d0db75bf5b203378f5946b
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.