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.
6185d85e44f46a2d86bbe619a2e56cf60340659296103a886f391fe0162a3199
Both payments are on their chains and locked to the same secret hash 8fdf6dc1c3e0ee58558724ae1ae8544545141e09, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 6185d85e44f46a2d86bbe619a2e56cf60340659296103a886f391fe0162a3199
- MakerPaymentSpent: 31ac596da79abecb487cc6c3fa060aa7044d49dcf5aacc1953da66d0a731ba83
5fb405aeda9e66670a755ba096a401a57576fa4d59fffd85a0065ff164558f0e
Both payments are on their chains and locked to the same secret hash 8fdf6dc1c3e0ee58558724ae1ae8544545141e09, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fe4c6c88c00a2c3207af511158ce9674c4e96999d03577af5280b1e8a93f52aa
- TakerPaymentSent · TakerPaymentReceived: 5fb405aeda9e66670a755ba096a401a57576fa4d59fffd85a0065ff164558f0e
- TakerPaymentSpent: 1b7f1b0bd78670e9c833baf45e3c69928bae7f8032078ef6aac539a7e76eb2ff
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.