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.
899945652959c1d733d0c96743d8123763f218d64febf2379d85a4855f1a24e5
Both payments are on their chains and locked to the same secret hash 377b3acd5c61bfa321f2c1e2187d8f02bae128f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 899945652959c1d733d0c96743d8123763f218d64febf2379d85a4855f1a24e5
- MakerPaymentSpent: fc8915492634cc8398f66eba1c191e9f8817f2af11d5efc8ac3b510566e52530
ee7786cfd21531bc2ec256914c56aa2fed6905cf4e3df3f2de757cabc03c3cfd
Both payments are on their chains and locked to the same secret hash 377b3acd5c61bfa321f2c1e2187d8f02bae128f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d37e2ab2adae40388c6907e16101aa2081193604552674c338aa6fbae0745f69
- TakerPaymentSent · TakerPaymentReceived: ee7786cfd21531bc2ec256914c56aa2fed6905cf4e3df3f2de757cabc03c3cfd
- TakerPaymentSpent: 6a93b094869391a2657c16bd02f1ae62eb3b557ee157b121c8d694daf2fdd51b
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.