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.
a98f465286e6928d7af4a2efa7c059b1ec76f5c68ad27843e4a2bd3f5181e95f
Both payments are on their chains and locked to the same secret hash 5dfffbd763d94ba18dc7f179c0176949ae38f69f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a98f465286e6928d7af4a2efa7c059b1ec76f5c68ad27843e4a2bd3f5181e95f
- MakerPaymentSpent: f0d557685f09444e9c641142811b7cc733a37af0c54bbfdc9265e984a1334bf1
a1d53c84f6d43e02ccd47385caadce3f1abe042068c0141608e4872e8c75f077
Both payments are on their chains and locked to the same secret hash 5dfffbd763d94ba18dc7f179c0176949ae38f69f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 79d9c21a3d22fb3914356457afa8fbfaf363846a8c0c99d6e977386eb0e0c291
- TakerPaymentSent · TakerPaymentReceived: a1d53c84f6d43e02ccd47385caadce3f1abe042068c0141608e4872e8c75f077
- TakerPaymentSpent: 0c0d606dc8e1be8e0091743063c6e71c7e15a74dacd1e154393ea228236f3e39
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.