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.
9b2c73560904dab253659a43bc00e53762936a32afec1790d4681300dcc3ef98
Both payments are on their chains and locked to the same secret hash 7cfbbfc786dd7880018a1190cd83942ab4ae456b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9b2c73560904dab253659a43bc00e53762936a32afec1790d4681300dcc3ef98
- MakerPaymentSpent: 731d9f23800cbc1571a7d821002847f31c13030953f0bd491b18b15d8d59bce9
d6e021d688fa0f35a77e06b20b9d68e08a3a71d02e71ec19e31dda2955c00ee1
Both payments are on their chains and locked to the same secret hash 7cfbbfc786dd7880018a1190cd83942ab4ae456b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 519c76aee4e46a9a9641957c56b27cd9e0d93cd4043c05b03d7088b79e4345cd
- TakerPaymentSent · TakerPaymentReceived: d6e021d688fa0f35a77e06b20b9d68e08a3a71d02e71ec19e31dda2955c00ee1
- TakerPaymentSpent: 7cc1aa9f29c882143097983c87ffbacb5b6572ab702ff0313c401286899b9f0d
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.