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.
3771515e6c069f25dcaa5f41f3b919b3352a4b6b859d44a61b8aed08785a9b5a
Both payments are on their chains and locked to the same secret hash 084e4bbc401004075522dc392d45567b7e6029b5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3771515e6c069f25dcaa5f41f3b919b3352a4b6b859d44a61b8aed08785a9b5a
- MakerPaymentSpent: 859a99837a18a6e266df099549efe012d800f100801552b58bff4a4755d6c8e5
8c0d0e421e4e3eb38e897a17c7001482a9fca8a9c751457020471f78dfbb8721
Both payments are on their chains and locked to the same secret hash 084e4bbc401004075522dc392d45567b7e6029b5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 809bdb3f2555d867e3eb032075fa8fb618e2640d5e83e5493c9fba99de7d66b6
- TakerPaymentSent · TakerPaymentReceived: 8c0d0e421e4e3eb38e897a17c7001482a9fca8a9c751457020471f78dfbb8721
- TakerPaymentSpent: 2b862fa881788305f2829bf00d086658073d705ccc90ef93707a924fe50cf7cb
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.