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.
4abef412ce89e4f5f6fcdcc8b266d6593f8f3efc639412fc5eba26f9351a800d
Both payments are on their chains and locked to the same secret hash 17bf2a420fba51d094da522c31306d7b443f3ca6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4abef412ce89e4f5f6fcdcc8b266d6593f8f3efc639412fc5eba26f9351a800d
- MakerPaymentSpent: a5f68932ceeedcd7cbabf325fb9ee079f8c4ea6d867df85ded087bd9d5331b13
d37977f4c14b9ab3c7eaff0dc884666b3e97c9df331687cc791ee2bcc4959acf
Both payments are on their chains and locked to the same secret hash 17bf2a420fba51d094da522c31306d7b443f3ca6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cb91a9653f898812b48152cc130e66924d0d3216429ed38a6a1e6ee62626c5ab
- TakerPaymentSent · TakerPaymentReceived: d37977f4c14b9ab3c7eaff0dc884666b3e97c9df331687cc791ee2bcc4959acf
- TakerPaymentSpent: bdca95d7f7baf6eb33c5b965f20e34756e31a120d6639e1114b056908ae558a6
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.