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.
22888d7380b91e3012cc9e020aec1db5ddf10607b2d8d5a644492078d9b68b88
Both payments are on their chains and locked to the same secret hash 53527af17ab5aabc217be90c598650409481141d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 22888d7380b91e3012cc9e020aec1db5ddf10607b2d8d5a644492078d9b68b88
- MakerPaymentSpent: 54688654d95b308a18a251714d29343ed50da86d77f73b9e6527312a454910f2
21690679ac5c650f375661744db845b321003e2974f3b1a4c08403126f92fb5d
Both payments are on their chains and locked to the same secret hash 53527af17ab5aabc217be90c598650409481141d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0d80cf70b59a0349a97d6fe0c3613974b372cce4264f7fa3530d9934476b2ebe
- TakerPaymentSent · TakerPaymentReceived: 21690679ac5c650f375661744db845b321003e2974f3b1a4c08403126f92fb5d
- TakerPaymentSpent: f8baf68947f53775197850ad89c4bbe81c9d5dc5155f9d2f3c7bdf32c2fc6ad7
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.