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.
2e02551daeec407dfb9eaacf5eee3a25ecabe52170a60a40bfbb29f5f767ddb8
Both payments are on their chains and locked to the same secret hash 1e286bc917799c65d0ea093637eb6248007b1262, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2e02551daeec407dfb9eaacf5eee3a25ecabe52170a60a40bfbb29f5f767ddb8
- MakerPaymentSpent: 9903388c9231e2af0379b130cb873fcef1fda64af9e237baac91764779c43c46
fa22c780ea3a9cb55db199def8aa5439e0786b46c03bcb1a54c13e1ffa794770
Both payments are on their chains and locked to the same secret hash 1e286bc917799c65d0ea093637eb6248007b1262, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 30d2e56f5aa751dc99503bccbbbca21e1d0201a3670f4d9037393c6129545f49
- TakerPaymentSent · TakerPaymentReceived: fa22c780ea3a9cb55db199def8aa5439e0786b46c03bcb1a54c13e1ffa794770
- TakerPaymentSpent: edf0701fa138643c869696260b30d2c12082534a59f08e8fcc624c941498a842
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.