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.
209e2bd49dcf36a25e649909ddd95a2179477b91f66799ed453af892b26cf460
Both payments are on their chains and locked to the same secret hash b731424ab563dab04928cbf89997bf7418c9f13a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 209e2bd49dcf36a25e649909ddd95a2179477b91f66799ed453af892b26cf460
- MakerPaymentSpent: 36b539adcb3a3a2498afb0843e890b950510c66c931a7eb4cec893f8662680f2
8109b99023b7d482846b43fe98312433fd58a7a029de643cb9461207a62a17fd
Both payments are on their chains and locked to the same secret hash b731424ab563dab04928cbf89997bf7418c9f13a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f921ec66968817642cc7e393d705c848468904e821afc3cd283058a3cef521e2
- TakerPaymentSent · TakerPaymentReceived: 8109b99023b7d482846b43fe98312433fd58a7a029de643cb9461207a62a17fd
- TakerPaymentSpent: fa8090a28a97c1a9c2a99e3c672bcf6f0eda95d55147607d0bb874cac32e694f
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.