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.
6ef074cb359176ad0b6f70d60c80c7c464a016dade397202b5f7ffdd42a3b3f3
Both payments are on their chains and locked to the same secret hash 65341d2b25ab257c71de00b2d07c6cffb67d935b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 6ef074cb359176ad0b6f70d60c80c7c464a016dade397202b5f7ffdd42a3b3f3
- MakerPaymentSpent: 125544fd6409120b16b3e3f07aa9c2a294b95cba9015f304a9e17e56a6e5df4d
f8aa5581278534f418fb03d840ab39d67e7743f5f8798779a9a662674a47a9e0
Both payments are on their chains and locked to the same secret hash 65341d2b25ab257c71de00b2d07c6cffb67d935b, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentSent · TakerPaymentReceived: f8aa5581278534f418fb03d840ab39d67e7743f5f8798779a9a662674a47a9e0
- TakerPaymentSpent: f164dd41256c71f654ac3312b2b584833ced62cbddb500d8f7b822267feb4397
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.