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.
197bcffee64fcc7ded5396f3a92037ad20402ce9b9a818577b72d7a92fb95f53
Both payments are on their chains and locked to the same secret hash dcb2028530409ee040423e80ff8393ccdee6809a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 197bcffee64fcc7ded5396f3a92037ad20402ce9b9a818577b72d7a92fb95f53
- MakerPaymentSpent: 851e7260414cad112c48f70b94450d0b3a0c7ac9cb14efe8caf3ab7846ac0cf1
9348ec33215b05295a0056084d96b7c30af36342335b0ecb12dbcaf37c750782
Both payments are on their chains and locked to the same secret hash dcb2028530409ee040423e80ff8393ccdee6809a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5d63c073071a3db0895b13809beec117656113835989c8e111ab0cab82bf9d0d
- TakerPaymentSent · TakerPaymentReceived: 9348ec33215b05295a0056084d96b7c30af36342335b0ecb12dbcaf37c750782
- TakerPaymentSpent: bf06056c2224ce1736078e5100a0947c1364a97ab9ff9b1309e1515c7a1642b0
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.