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.
476840f48516325c53e21704f40dd2c02a8afa2e7668c34d90b3a039464faff5
Both payments are on their chains and locked to the same secret hash 42e9762a24c0249d1ed0f70d67b1886d567637e0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 476840f48516325c53e21704f40dd2c02a8afa2e7668c34d90b3a039464faff5
- MakerPaymentSpent: 067193560d0599bff507350451815ece2a9d1ae5f2d4ac61e091edad97b50e44
b06d47cf380e834781d6bb19e2997cebbabf69722e6ecf75bae56770d0f5b1e8
Both payments are on their chains and locked to the same secret hash 42e9762a24c0249d1ed0f70d67b1886d567637e0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e227f63068cd3a038270ffbd7a7d4772e8073241d3bb13781b492d4a4f79c181
- TakerPaymentSent · TakerPaymentReceived: b06d47cf380e834781d6bb19e2997cebbabf69722e6ecf75bae56770d0f5b1e8
- TakerPaymentSpent: 62a13b0f378ccfb1b5341b3ad710b767766aa7fca4ce9670c50e52c0a2440a97
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.