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.
37f7273d22159932dfed1c4c0d46f14b52ff4bcf6d793a68b22c16a51d354dcb
Both payments are on their chains and locked to the same secret hash 308c72d0f94e362453edd41fe5647951c886f444, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 37f7273d22159932dfed1c4c0d46f14b52ff4bcf6d793a68b22c16a51d354dcb
- MakerPaymentSpent: c91fbf5150fb22ce4dc3d7a847edbabd6968b1002e61361890be6089109880d7
ce01e20ad88bdd3800a622e0e89648e4d6461c5bcff62099783a90cf4590780c
Both payments are on their chains and locked to the same secret hash 308c72d0f94e362453edd41fe5647951c886f444, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8c187fd2ccf36cf76672633a6422ccdd92f5d7e7f4c4d67be48bc030f4f1845e
- TakerPaymentSent · TakerPaymentReceived: ce01e20ad88bdd3800a622e0e89648e4d6461c5bcff62099783a90cf4590780c
- TakerPaymentSpent: e5850fd3479b8e8cfe97acaf52f83c69ed02150db049bd921ebfa7fd3a8f0f30
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.