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.
2bf8ce39a4812fc0168ce6ae69fa80e08cad522b7e184341bc241d21eade5524
Both payments are on their chains and locked to the same secret hash 53b8257a12b25acd0ebde59811157c8957745def, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 2bf8ce39a4812fc0168ce6ae69fa80e08cad522b7e184341bc241d21eade5524
- MakerPaymentSpent: 9da45e1e70622df067529209e91049ce0f2affbae62e150d466e4cf2b6eef5de
ebe22939187576429de858e84d5924b8a929709d6104081f9fa37b473d04f4be
Both payments are on their chains and locked to the same secret hash 53b8257a12b25acd0ebde59811157c8957745def, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 286a483c024d4f75f4776b17e4121c37ae7c40feee3502f753fa457c43c22f8d
- TakerPaymentSent · TakerPaymentReceived: ebe22939187576429de858e84d5924b8a929709d6104081f9fa37b473d04f4be
- TakerPaymentSpent: a279e9e33f0d5b2888afbb87a24b448177e2587544244e90b6e490df061e1572
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.