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.
e8504b72659640d57a91a1fbf15b500b01e4ff8346f47ec65a1b636a4f993d92
Both payments are on their chains and locked to the same secret hash fc5f3542d7f427844109a9966ef68e7c6420779f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: e8504b72659640d57a91a1fbf15b500b01e4ff8346f47ec65a1b636a4f993d92
- MakerPaymentSpent: 32a1108d7e46039c5a96a822dc27b08b14d5bcb4de3d21f813973297a22f4965
6a81a36590acc8437f558eb9867c3235151d4b387cf7e0ef0c26c5fdf21a886c
Both payments are on their chains and locked to the same secret hash fc5f3542d7f427844109a9966ef68e7c6420779f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 79ba58de650b6c331b00db179f746050ebda7924dadbb20eebf6c5882fa52a5d
- TakerPaymentSent · TakerPaymentReceived: 6a81a36590acc8437f558eb9867c3235151d4b387cf7e0ef0c26c5fdf21a886c
- TakerPaymentSpent: ff16e7eb76ddeaae9922ee19e5fc27be69fa441616851776044521f13879bc7c
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.