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.
6e5e0251f355c1a3b3e7a4f154b7621c7ea39f8d3fbc9a0bdf16d339d9295b49
Both payments are on their chains and locked to the same secret hash 59749c5c063d4edc509a9990d69850c747fc8361, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6e5e0251f355c1a3b3e7a4f154b7621c7ea39f8d3fbc9a0bdf16d339d9295b49
- MakerPaymentSpent: a75fe628c3a65db515db41035c07f78d6faf6c9b1ccaa6f20846c661392dba78
2c57903a710aa4d02621b506eb25951c5a7239301f8e1852a85bbefa0b4030f8
Both payments are on their chains and locked to the same secret hash 59749c5c063d4edc509a9990d69850c747fc8361, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 882167371c3749b6c432259c06b6c74f77310fa2ab733fa0bae0d7ed6366c0cb
- TakerPaymentSent · TakerPaymentReceived: 2c57903a710aa4d02621b506eb25951c5a7239301f8e1852a85bbefa0b4030f8
- TakerPaymentSpent: 942e8d3c01a72acd39c070d999d82226f354488d71bb29b1222f395930724dd0
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.