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.
a0aee0ee21ac8f038cf6df6bf669e69ddc38a17395e784cfadf8937b20d851fa
Both payments are on their chains and locked to the same secret hash d267df10800187768cc245b2ecb4d961ab99634a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a0aee0ee21ac8f038cf6df6bf669e69ddc38a17395e784cfadf8937b20d851fa
- MakerPaymentSpent: 7f447b46d080fc09cbdc250230c1b19abf8e23404b0e21a72151354993848218
bc434d259bd947a4868bb0bc5a72636b44c65a5397d95d84dbcf500b57ce46df
Both payments are on their chains and locked to the same secret hash d267df10800187768cc245b2ecb4d961ab99634a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3893af21ba766bab5f2de096383442b8901e97186191d223f95ba557e77ffe89
- TakerPaymentSent · TakerPaymentReceived: bc434d259bd947a4868bb0bc5a72636b44c65a5397d95d84dbcf500b57ce46df
- TakerPaymentSpent: 2c4f80f4aecf088fb9409180b10c37480f999b7afd6cfca8023571c933580701
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.