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.
52ad6b74753b58416e52833ef1ebc8f34d08978c4102f1ca5e47aae938951db6
Both payments are on their chains and locked to the same secret hash 109fc5ff9f50808f497df252703e21787265add6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 52ad6b74753b58416e52833ef1ebc8f34d08978c4102f1ca5e47aae938951db6
- MakerPaymentSpent: 774647337a0313a1b7bbbf35a0eef8bbf6e35dab95b5012da6a1b7eecf4ff68c
4d19cfabe59ec64c71ee179bf8a22b6c273d101069655caded9e6645587648eb
Both payments are on their chains and locked to the same secret hash 109fc5ff9f50808f497df252703e21787265add6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9c4af43b533289f79a463e24931e678a502ea6eac871f81b5e8918a5fc17add1
- TakerPaymentSent · TakerPaymentReceived: 4d19cfabe59ec64c71ee179bf8a22b6c273d101069655caded9e6645587648eb
- TakerPaymentSpent: 4934d47df5d1c063e9ef37e9bcaf70d2e3170c0b1106c731232bf273bb7a9f4f
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.