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.
ead21b0cad5129645ca76a9936b9effdf3951b70a47f4440d178138ebd2f4756
Both payments are on their chains and locked to the same secret hash 86d0f01553a083e72e1e60a368fe305a618d6973, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ead21b0cad5129645ca76a9936b9effdf3951b70a47f4440d178138ebd2f4756
- MakerPaymentSpent: 1c7a768ccc53d004683102a953af6221ca82795feaef9cbb8fdb33716ee6b522
916162ff672f4ea089885f4fd297d6b50a69b904cb2566d0d60a091ef766e94b
Both payments are on their chains and locked to the same secret hash 86d0f01553a083e72e1e60a368fe305a618d6973, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 987015765837ae57612479fcfb05afeddac831092ac435f22effdcef82053d0b
- TakerPaymentSent · TakerPaymentReceived: 916162ff672f4ea089885f4fd297d6b50a69b904cb2566d0d60a091ef766e94b
- TakerPaymentSpent: c300eb1d18b2054dffc48d4ec27c56d941da566388796b277eb820cfed9aee44
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.