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.
18387ee8eed1020d0ec1ec5ddf51cad71eba433f954970369f188e8d4cccf784
Both payments are on their chains and locked to the same secret hash 985b39864a924c7a849b95a6cbedd0bf3c9b503a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 18387ee8eed1020d0ec1ec5ddf51cad71eba433f954970369f188e8d4cccf784
- MakerPaymentSpent: a64435232ecdb4eb178e52fb43588d7ae51e7a0c1bfb412679c09a77d22fe96a
217e6f10088903833ac236f5cbcae1c1ec2b7853071cbeae89e6bbc0ab54c342
Both payments are on their chains and locked to the same secret hash 985b39864a924c7a849b95a6cbedd0bf3c9b503a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7fd3ccd392ca56fec5168543b45ac376dd809070c096e7c67c6f71e1f119daac
- TakerPaymentSent · TakerPaymentReceived: 217e6f10088903833ac236f5cbcae1c1ec2b7853071cbeae89e6bbc0ab54c342
- TakerPaymentSpent: 1ed8607f4dde3f007e7f1bf7997de5f4c4162b81135effd6f24230ff17ded0dd
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.