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.
d771a4f1dfc2493b2c4ef9badc8bb32bec381c83bd2a9667c30a41c310dc5533
Both payments are on their chains and locked to the same secret hash 3c46344b1eb7e610bee000de741f400c711f84c9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d771a4f1dfc2493b2c4ef9badc8bb32bec381c83bd2a9667c30a41c310dc5533
- MakerPaymentSpent: 1733735e742b69c09ff5e596c9b77df515bf03b1ae8e5b1a25ce04812689de49
b1353ea9757c75f094f4c703e92bcd99518a73114edce9bcd85ff0e66a06eaa5
Both payments are on their chains and locked to the same secret hash 3c46344b1eb7e610bee000de741f400c711f84c9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d5bc6c30348f7d0f377e6e4d371b0c547af4bffafe27d881ca8ac5044dfea33f
- TakerPaymentReceived · TakerPaymentSent: b1353ea9757c75f094f4c703e92bcd99518a73114edce9bcd85ff0e66a06eaa5
- TakerPaymentSpent: 4b1e6e421f6e3e2ad223d3fc48248f51029de83dba9f8926a5b7320751deb9c1
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.