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.
1e3232e29a02248e456af36a155d519344a81aa9515f885680b05678104b2f02
Both payments are on their chains and locked to the same secret hash fb1a6897c2b9c225681708d4675b2b771366572f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1e3232e29a02248e456af36a155d519344a81aa9515f885680b05678104b2f02
- MakerPaymentSpent: 53915a927d672ef790747bc11c68044a7a7e85b6702b3a88b65cfc53ee5a3bab
5970ee3497aeaaf25dbd445e76797a2700b7b25bf0c4fdff914882bd3c515c1c
Both payments are on their chains and locked to the same secret hash fb1a6897c2b9c225681708d4675b2b771366572f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f03d6b5c3f1eb01c9fe8576c78f3627e87f8eb3852977b84ba01b24293036980
- TakerPaymentSent · TakerPaymentReceived: 5970ee3497aeaaf25dbd445e76797a2700b7b25bf0c4fdff914882bd3c515c1c
- TakerPaymentSpent: 1812d3e1675939aea102b31047ce41527524229d182c6c68c3ed4cebb1685ca3
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.