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.
849d73cd845e48e58910aee932cf6747b9e776893b363f44fbd0fd888b0d5971
Both payments are on their chains and locked to the same secret hash 252357346caaa6d826fec0ef8ad71c7cf4c57b83, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 849d73cd845e48e58910aee932cf6747b9e776893b363f44fbd0fd888b0d5971
- MakerPaymentSpent: 7d2e5fb736ed77fd9ccd5b024778b3edc30acd814a9c2253960a04593e992e8b
052c667b14eddf71cdf6631580a28318e2ef85e18ff9ea0d69fbfe39e6bc6184
Both payments are on their chains and locked to the same secret hash 252357346caaa6d826fec0ef8ad71c7cf4c57b83, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 654e7c1a0be09273aa5807118d8aae648be4b1a7ca444421f9352c802bc9f446
- TakerPaymentSent · TakerPaymentReceived: 052c667b14eddf71cdf6631580a28318e2ef85e18ff9ea0d69fbfe39e6bc6184
- TakerPaymentSpent: ba2568288d5e4bec35ec6e0cd772794cf8fee41ee59d00c57d76527c7b6f41cf
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.