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.
f88f928bc87bb09272760e9fb97572fc5e259ef25cdd100312eefc4ff8d8c8f4
Both payments are on their chains and locked to the same secret hash 667bd53c829191bcbaa92e7534bd594d97646ddb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f88f928bc87bb09272760e9fb97572fc5e259ef25cdd100312eefc4ff8d8c8f4
- MakerPaymentSpent: 4e3d8d8062332275d5c730262520eb97d4b5b642c1cd0717507d309e7a18051d
c764002a68848df484da52da998ec256e777fda9e69b3dd4b2ded9af414981d6
Both payments are on their chains and locked to the same secret hash 667bd53c829191bcbaa92e7534bd594d97646ddb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 69d3b2a790a2e4531d875960f4dcf7c3546c715aae2a9f9baca89e75eb13d698
- TakerPaymentSent · TakerPaymentReceived: c764002a68848df484da52da998ec256e777fda9e69b3dd4b2ded9af414981d6
- TakerPaymentSpent: 69cfb834ef3b94431cdbddafaf9109d29a5c37218252e82ceadfbe546a354d16
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.