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.
d45d9673eba2a0e8ff515aa876659b2d390c2b5af457d0ff30dd0bfa6b5fa154
Both payments are on their chains and locked to the same secret hash 2cadbbeaa1e40af1410d6461f98e9b329f1e1825, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d45d9673eba2a0e8ff515aa876659b2d390c2b5af457d0ff30dd0bfa6b5fa154
- MakerPaymentSpent: 666e8d677bb4e373183b30d39e4a4ecb5ec818146b4eb46b01f645088e1dfa02
8a8060147b1373dc7befad70965d5c1d8a63207cfdab07a211b6379b5ad39202
Both payments are on their chains and locked to the same secret hash 2cadbbeaa1e40af1410d6461f98e9b329f1e1825, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 10ead9e146fbcc6d5e4793a483535e00b9c6a86f49fe179aef2846ed3e1b3176
- TakerPaymentSent · TakerPaymentReceived: 8a8060147b1373dc7befad70965d5c1d8a63207cfdab07a211b6379b5ad39202
- TakerPaymentSpent: 54aecdb649bf7decc30b97960173d9621e28028d802af4a2527852d2be8dfdcb
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.