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.
2233762d568d7da0b9b9f37b45d63cb9e44f99a9c6fc80446a1ecbb7e887d3e5
Both payments are on their chains and locked to the same secret hash 944faf137a27883007fc7b1cb0621aa71be98c30, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2233762d568d7da0b9b9f37b45d63cb9e44f99a9c6fc80446a1ecbb7e887d3e5
- MakerPaymentSpent: 637adab270a5eca207599aaea0edbaf49a758b6e740dbf69e01a7e29aba26ae3
ad944f9ae5cf66f7742ae0ac6f16fe44d7bf87a4d35024f91e1fda5fdf4d3afb
Both payments are on their chains and locked to the same secret hash 944faf137a27883007fc7b1cb0621aa71be98c30, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bdce8f309de0c674a4e16e63d21af89f1b352546c51e5fa923f060ab6ea5e54b
- TakerPaymentSent · TakerPaymentReceived: ad944f9ae5cf66f7742ae0ac6f16fe44d7bf87a4d35024f91e1fda5fdf4d3afb
- TakerPaymentSpent: 58017e8c1d3003a17bcd258e22202761276fc346eadec0d32e05d9ca79d05b7b
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.