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.
adc2a13d1ac0a9447c95df3702949d5ec5c433ff0979cf41e38ff8b70debdf80
Both payments are on their chains and locked to the same secret hash f1e631f6ccc02e7478c80ca504bfef960982e6a4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: adc2a13d1ac0a9447c95df3702949d5ec5c433ff0979cf41e38ff8b70debdf80
- MakerPaymentSpent: e15021963033c5ee82056b89ef64654f6e7d3f45a2a813ecc707ff0810b14b80
daa038c557422feb9253773bee7f74d8b35001c86f2a4c023c9d94baa33543c3
Both payments are on their chains and locked to the same secret hash f1e631f6ccc02e7478c80ca504bfef960982e6a4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ddfec973711f90d9a56581e3f29f9b2eb1ff95c9540d01eb823e1b3874d5c3fe
- TakerPaymentReceived · TakerPaymentSent: daa038c557422feb9253773bee7f74d8b35001c86f2a4c023c9d94baa33543c3
- TakerPaymentSpent: b89698a87260f7eff601c83208744dce6e952fa6b6ea48ecb8a362504d1434e4
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.