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.
953abf6e18b8ad4819ef982c5fd9050ef1cc7879f77cf68ee9e5dfd69d78435f
Both payments are on their chains and locked to the same secret hash aa1d81b138636cd59dfd104ad376a791765061db, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 953abf6e18b8ad4819ef982c5fd9050ef1cc7879f77cf68ee9e5dfd69d78435f
- MakerPaymentSpent: c8ff02b0747ca864d81089f80dfa2a50ade8371f1950b39d6c38a1e2a2abe9c8
5b306e90203c2faac6da16b5266684d71f5cb30df5e3cf515b92b529a95a2881
Both payments are on their chains and locked to the same secret hash aa1d81b138636cd59dfd104ad376a791765061db, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0a4c7798cbec0c942a847d9c77cabe819582680dfb3153af4e4817d5bb623de7
- TakerPaymentSent · TakerPaymentReceived: 5b306e90203c2faac6da16b5266684d71f5cb30df5e3cf515b92b529a95a2881
- TakerPaymentSpent: cbe7ea25ab480c0dff94f3354b9300065a3d2b0d30d02860341c61852ffb6f54
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.