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.
812c537472940e0cf0e34b60b6d57f0e56a8ce381ee88e8f78b32d20e98c3d4c
Both payments are on their chains and locked to the same secret hash 41d57f3258419b67d7c94752f6e130d7e3f7d2f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 812c537472940e0cf0e34b60b6d57f0e56a8ce381ee88e8f78b32d20e98c3d4c
- MakerPaymentSpent: 76c0d6138caba0291c8bd4b67c39b573707d0fa75e7b26c36080ffb55b883827
d09e9ce6d6d08e502b7115eacbd57cd5d2dfb4d10a6a156b092df94cfc379499
Both payments are on their chains and locked to the same secret hash 41d57f3258419b67d7c94752f6e130d7e3f7d2f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5fd97196e278af7511dc99ab41763199d028e16b5f228d8dcbebbf426e736f2e
- TakerPaymentSent · TakerPaymentReceived: d09e9ce6d6d08e502b7115eacbd57cd5d2dfb4d10a6a156b092df94cfc379499
- TakerPaymentSpent: 37ec5d725277cdc8a9f5ae2e39da4b8ad6a9e12266c13431e3eacf40be43c54b
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.