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.
1bfaa43946096d18860d6fd27d287df513cf36f61f901ffaf8ec7b661d985f49
Both payments are on their chains and locked to the same secret hash 7d063296b79c6b84c8b4fc78120a9caf5fb461d1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1bfaa43946096d18860d6fd27d287df513cf36f61f901ffaf8ec7b661d985f49
- MakerPaymentSpent: d90e19ad2980a47bffec3dbc15dfe50572342abfbd29a894a98515b4222bb310
d268be18c4582f1bac158caae1d511638e40280f618b42992ed9d678f7e3226c
Both payments are on their chains and locked to the same secret hash 7d063296b79c6b84c8b4fc78120a9caf5fb461d1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c077809c38acfa70d275e6869cf2addc36956a12ceaaaf72301fc5e0de09d726
- TakerPaymentSent · TakerPaymentReceived: d268be18c4582f1bac158caae1d511638e40280f618b42992ed9d678f7e3226c
- TakerPaymentSpent: a155752779776485932b60d6948275e29b1633c331013934bbf6bfda9380139c
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.