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.
05c18a8e7c226960379b6c57157e1e07722861af42ed97aaa1fc4470191fbfef
Both payments are on their chains and locked to the same secret hash 925861f2d53839592354ce803d385f0973c603f6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 05c18a8e7c226960379b6c57157e1e07722861af42ed97aaa1fc4470191fbfef
- MakerPaymentSpent: d00683073284a5deb045af8636619ef65f0203924f40cd792e9aa1fd4206b035
266d0856bbe695a2e461dc33925d554a19045e6baf2b504548c27cd75d0fd906
Both payments are on their chains and locked to the same secret hash 925861f2d53839592354ce803d385f0973c603f6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 66206b5fb7b722d8aef1571bcb3021942a65639d627c00aa2da67a1b376517d2
- TakerPaymentSent · TakerPaymentReceived: 266d0856bbe695a2e461dc33925d554a19045e6baf2b504548c27cd75d0fd906
- TakerPaymentSpent: 2b47e8866c64e174ac3df1fa51dc110029fbb68e6e1ca2f358c5bfd8c07ef4be
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.