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.
75a88d6ba5757931ad4d2672b2bd2031d99729a422e9f11471aab9516a7222ca
Both payments are on their chains and locked to the same secret hash 8903469d9c8821b952662d56c98a647d5386dcda, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 75a88d6ba5757931ad4d2672b2bd2031d99729a422e9f11471aab9516a7222ca
- MakerPaymentSpent: 03ded8d9f88417e404310faefb5b2b3cfb70cabdf3f1c9a6555f05b4e36ef708
226598a489db33e359ed127670bbe00b915ea23555b43b78c20979e28a508ab2
Both payments are on their chains and locked to the same secret hash 8903469d9c8821b952662d56c98a647d5386dcda, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 57e6a7ba03fdc4f293d8f4aed3d030c8a7151399c6955d93479e2fbb5d7af34d
- TakerPaymentSent · TakerPaymentReceived: 226598a489db33e359ed127670bbe00b915ea23555b43b78c20979e28a508ab2
- TakerPaymentSpent: ef89236bd2af4d0e80063c86756eb82eb3de0e7efb066917151dc78df21103f4
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.