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.
12ace701e8a64a71cf4b38e59715af2733d78f39b834348982d458b5fa479c64
Both payments are on their chains and locked to the same secret hash efad19242d07112605253a6d318976ea4a737c55, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 12ace701e8a64a71cf4b38e59715af2733d78f39b834348982d458b5fa479c64
- MakerPaymentSpent: 637f575412fdaebc2b9877b7b998b7c0e2a0ca2934c393f1770051c01cbe5d2f
8d388498487887dbc5fa516a1599ee55683aeb32f9ef55ed068fb9ccf168eead
Both payments are on their chains and locked to the same secret hash efad19242d07112605253a6d318976ea4a737c55, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b7690d6e6b2b27aff29454ebe8b3f056ffd407527b76518d001322a610b00420
- TakerPaymentSent · TakerPaymentReceived: 8d388498487887dbc5fa516a1599ee55683aeb32f9ef55ed068fb9ccf168eead
- TakerPaymentSpent: 15b272805a8fb2fc1ef209b0c34844890bcd388417fa51bedc5fc91634cbf93f
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.