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.
16e39b5b6b51b1cf10f8fe83707238601929467b2dee45608d92670a6acee667
Both payments are on their chains and locked to the same secret hash 05f516e5b52ac8290555973695623510d5be5926, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 16e39b5b6b51b1cf10f8fe83707238601929467b2dee45608d92670a6acee667
- MakerPaymentSpent: 11fd153af63b724fe2627a07ea923a949c37077fa4feed82229aa6ca8751fede
21abfb624cb46b0612e3f66b0ad4e6a93dabbbbd734b6b0d3590a9ba7b168606
Both payments are on their chains and locked to the same secret hash 05f516e5b52ac8290555973695623510d5be5926, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 91a8bee2a769762cbf757f55d21c2b7d62b2a96006d6b331ed8720bea2de0e74
- TakerPaymentSent · TakerPaymentReceived: 21abfb624cb46b0612e3f66b0ad4e6a93dabbbbd734b6b0d3590a9ba7b168606
- TakerPaymentSpent: bd0694a9b8661c09ef377094363a072f82cead9c13da61da2949f6c4ebd36adb
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.