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.
e6bc59dc86db1c56a185ceef20bcf7caee7a28f40847c7d73e560692801c73b9
Both payments are on their chains and locked to the same secret hash d4e95a5b5e0cca4a92d01585466f478fb301fc61, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e6bc59dc86db1c56a185ceef20bcf7caee7a28f40847c7d73e560692801c73b9
- MakerPaymentSpent: 1d59c4097f08b9c37273a9122b09eb05df5a8339cc3a78e4949b8f925e08d3d6
f97c88a0d374a6cf0f770c9d386dacd39f1a7bb51d4c758fdeed51eeb0bbdc43
Both payments are on their chains and locked to the same secret hash d4e95a5b5e0cca4a92d01585466f478fb301fc61, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 327828ed81cd02bc0919b39c95b048139a573af54573f30d7f12f818302e89f6
- TakerPaymentSent · TakerPaymentReceived: f97c88a0d374a6cf0f770c9d386dacd39f1a7bb51d4c758fdeed51eeb0bbdc43
- TakerPaymentSpent: c0897314d0d77515851a6b84e755627aa0b4dc7db75c855f82d24e4114f1fbdf
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.