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.
fe5b75e2581f1cc9752e0448027383982613cd6ff38de5c2764f8e3a4601f2f2
Both payments are on their chains and locked to the same secret hash fbf40a8b740850177132e6c5211ce28e97efbbc2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: fe5b75e2581f1cc9752e0448027383982613cd6ff38de5c2764f8e3a4601f2f2
- MakerPaymentSpent: b457e2c676f49d60ffd6550ccf3b8ae177b95686f7404b92979c426c9681ca89
29f755e736911a1a6ba7f177455895ccd6e13699f82bc39f9ad15665e21af651
Both payments are on their chains and locked to the same secret hash fbf40a8b740850177132e6c5211ce28e97efbbc2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 545f05348ac0bc939396794d1af01e8e4504bae17852ed77de5d57283c2451f6
- TakerPaymentSent · TakerPaymentReceived: 29f755e736911a1a6ba7f177455895ccd6e13699f82bc39f9ad15665e21af651
- TakerPaymentSpent: c3a9f674bde20a17b8fd3007186b3afae10b484006cf563df6d45b6d5944babe
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.