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.
aef2457ac62dcb95ddf05ca9d2f648ba044a86a2437848d08973379d64fec202
Both payments are on their chains and locked to the same secret hash 4b61d15ff4f5335f653db2e099c4ad44a696ae70, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aef2457ac62dcb95ddf05ca9d2f648ba044a86a2437848d08973379d64fec202
- MakerPaymentSpent: e33ae831673f99001cbd19d031b25bd4ed3424ff42164669a2765414907619a8
c46ed923b17cce9afbeb6ce4b6f1316260d6f1b5e739a1f1687bcc82f49ef888
Both payments are on their chains and locked to the same secret hash 4b61d15ff4f5335f653db2e099c4ad44a696ae70, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 007e2a461c32c8abae902f08651001a85875ab03a3174ce45de0aee6a3b8f0b6
- TakerPaymentSent · TakerPaymentReceived: c46ed923b17cce9afbeb6ce4b6f1316260d6f1b5e739a1f1687bcc82f49ef888
- TakerPaymentSpent: 44d469b807917607764d5dcd1fe96b6fdc87b3224c12dcb7ab2b1ef3751a055e
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.