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.
38995ffe3cf0f1599cef53ae366fc36b69b1defcd708b5092592b63178b21dff
Both payments are on their chains and locked to the same secret hash 8e9d56b0f36083b5a47ef559a499340d729b4c9c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 38995ffe3cf0f1599cef53ae366fc36b69b1defcd708b5092592b63178b21dff
- MakerPaymentSpent: e1578a47570d079d3974f87bc5f1e051018d204c9fd5c75d9174a20651f005f2
5692dda0e572f99503528848912cbfc08392550e79ceda560ef2f399ff363218
Both payments are on their chains and locked to the same secret hash 8e9d56b0f36083b5a47ef559a499340d729b4c9c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1b1b651d6d8df9aea5d2440846e86484409ee42fe58e294349e35ddbce44532c
- TakerPaymentReceived · TakerPaymentSent: 5692dda0e572f99503528848912cbfc08392550e79ceda560ef2f399ff363218
- TakerPaymentSpent: a179cd1ddc179cfe0b16cb32e6450028b2192b8bfc147e42404ccde69b9d872f
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.