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.
da853921bb8234cd295fa45497f6688566efde1b9804e51dc95e853bbb0f4cfd
Both payments are on their chains and locked to the same secret hash 340bf62598c63087f035ee94373034584b7e5311, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: da853921bb8234cd295fa45497f6688566efde1b9804e51dc95e853bbb0f4cfd
- MakerPaymentSpent: 4cfd2b64ba193ae2d5544f5b8abde82439408445ff9ea1b5c670ffc9e8b77185
867adaff7fb9efb91cee6dad7e0149507d176682ba3bd04561a53532b6779ced
Both payments are on their chains and locked to the same secret hash 340bf62598c63087f035ee94373034584b7e5311, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b95f852437771d00193ac45c114406886a2e90c17b4d094ff8feaee4acd73db1
- TakerPaymentSent · TakerPaymentReceived: 867adaff7fb9efb91cee6dad7e0149507d176682ba3bd04561a53532b6779ced
- TakerPaymentSpent: 8c9bf82f8ac22290f17fd966a855d9d835efaef2a3665f58e405e9b97f241fa4
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.