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.
ff659089568340f3bc43bebafbbfed618fc7612fb8eb73f9d5ce5cf2e8f43a79
Both payments are on their chains and locked to the same secret hash 1aaa924cb81442afa42022490be976a45a60ed80, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ff659089568340f3bc43bebafbbfed618fc7612fb8eb73f9d5ce5cf2e8f43a79
- MakerPaymentSpent: e590d788bd51abe36593827a1ba5bc6391c2e97f42141ad3e6a1e231f6de863a
76417968117c97287d53e7e965757a0bb777bd9c14f0d53d78c3e2a334cfef18
Both payments are on their chains and locked to the same secret hash 1aaa924cb81442afa42022490be976a45a60ed80, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9276ae69dbd8b2d87048d9a36ed23bb697040708651391763a2f2950ffb5d55c
- TakerPaymentSent · TakerPaymentReceived: 76417968117c97287d53e7e965757a0bb777bd9c14f0d53d78c3e2a334cfef18
- TakerPaymentSpent: f794939b015975e502cb05dac27c0db081440f46f14e6a23702dc340cfa49764
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.