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.
154250127975424c93553842a051e83e98aac01b98708b227c7b6dd1cf12e3b2
Both payments are on their chains and locked to the same secret hash e84b6641bec19447a0ace8b5bb6c7b0d1a0ecafd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 154250127975424c93553842a051e83e98aac01b98708b227c7b6dd1cf12e3b2
- MakerPaymentSpent: d2515c8e90aae75375de401cedc03c6922e73525aa8998a6229d6d77710ad50c
53ac2cb4bec38b3a75c22b2a9b29326a0f231c4303f534a2dfe314c1fbecaaaf
Both payments are on their chains and locked to the same secret hash e84b6641bec19447a0ace8b5bb6c7b0d1a0ecafd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ecae0506e1e7a44cfe4a129b9daa08dc27c930bb9d73880fe62074aa82a6aacc
- TakerPaymentSent · TakerPaymentReceived: 53ac2cb4bec38b3a75c22b2a9b29326a0f231c4303f534a2dfe314c1fbecaaaf
- TakerPaymentSpent: a686eeeedab4c6da6f499f53a4e2add90a3f55e7e0d67cbcc00a83aacbce91d7
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.