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.
f148af2f0ac84aecb0b822beac133597376bfd986a5ef772342701ffdfd006ee
Both payments are on their chains and locked to the same secret hash fccf03a6c3cd9c17cc9f5ef129dfa1402bb67b0a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f148af2f0ac84aecb0b822beac133597376bfd986a5ef772342701ffdfd006ee
- MakerPaymentSpent: 37ff02d8c30109f8db60f521c341b9a75f9d39bf94fa6d6f5fbde4963260c51e
e6416b463686d262078ccccd68bb5e824992ef90007345deddafd4f7758746ad
Both payments are on their chains and locked to the same secret hash fccf03a6c3cd9c17cc9f5ef129dfa1402bb67b0a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bba9eedd0f7532a66ed89e45177ab6caeab70d6269057743792285026f50311c
- TakerPaymentSent · TakerPaymentReceived: e6416b463686d262078ccccd68bb5e824992ef90007345deddafd4f7758746ad
- TakerPaymentSpent: 7db1813b6de7339099dceb6e93aae2f93d18e4a04e362e7f5ec2e7f7c1f6de87
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.