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.
56903665f253640618c9f72abb4387788a25f3cfe65671407e5bd9ad64cf36fb
Both payments are on their chains and locked to the same secret hash 4b00dd2643818d533d1310218e1108b61e1193b9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 56903665f253640618c9f72abb4387788a25f3cfe65671407e5bd9ad64cf36fb
- MakerPaymentSpent: 8d29e53875cead80a36ebc66df5758041fea2463d80aaa7b39a603fac5606485
82ecfd3fda8be04fbb84c32c987e9a35bf55c932d43e27086f88e9a8f1260498
Both payments are on their chains and locked to the same secret hash 4b00dd2643818d533d1310218e1108b61e1193b9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: adcab0c99ac165c516444a070874146d7f7d7a8f1016a1151f37e345575f8329
- TakerPaymentSent · TakerPaymentReceived: 82ecfd3fda8be04fbb84c32c987e9a35bf55c932d43e27086f88e9a8f1260498
- TakerPaymentSpent: 7a42ec2ea656d4ac5a7d8d766f7e0979735f0ce584605cd11da4ad6f5e6dde54
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.